[rancid] Juniper 'last commit' + Fortigate whitespace + DB

[heasley]

Mon, Oct 23, 2017 at 07:42:16AM -0500, Chris Wopat:
> On 09/29/2017 09:54 PM, heasley wrote:
> > Fri, Sep 29, 2017 at 07:28:27AM -0500, Chris Wopat:
> >> Hey folks,
> >>
> >> We recently updated to 3.7, a few comments/questions.
> >>
> >> * Juniper was updated to ignore 'last committed by' line. Changelog
> >> says 'useless
> >> last commit config line'. Curious what others think about this. We think
> >> it's quite valuable and is a nice way help correlate changes to accounts
> >> that made the change. For now we've manually restored it, which is easy
> >> enough.
> > 
> > there is only one way that that token can be guaranteed - if rancid were
> > guaranteed to collect the information before anyone else could run a
> > commit.  if folks really like that ...
> 
> We didn't have an issue the way it worked prior, I'm happy to just 
> continue to manually patch this back in.

you realize that the output may be incorrect?

> >> * We see the 'show chassis firmware' line come and go on some devices. This
> >> happened prior to 3.7 as well. This has been witnessed on MX running 15.1,
> >> QFX running 14.1X53-D45, and possibly other devices.
> >>
> >> + # show chassis firmware
> > 
> > hrm, what model MX?  I've not seen this in the lab or production for mx
> > or ptx.  perhaps we can chat about whats different in your env.
> 
> A few MX960s, with RE-S-2000 and RE-S-X6-64G, QFX5100m EX4200.
> 
> A few examples below of some 'show' commands toggling back and forth:
> 
> 
> Index: configs/r-mx960-lab
> ===================================================================
> retrieving revision 1.1162
> diff -u -4 -r1.1162 r-mx960-lab
> @@ -1,8 +1,7 @@
>    #RANCID-CONTENT-TYPE: juniper
>    #
>    # r-mx960-lab-re1> show chassis clocks
> - # show chassis environment
>    # r-mx960-lab-re1> show chassis environment

This tells to me that the login script is out of sync with the prompt.
Could you show me output from:
	eval `rancid -Ct juniper device`