[j-nsp] JUNOS upgrade annoyance...

[Melchior Aelmans]

It sounds to me as if you want to file an ER with your Juniper account team
;-)

On Thu, Aug 1, 2019 at 2:59 PM Chris Adams <cma at cmadams.net> wrote:

> Upgraded JUNOS on an MX last night - I had put a python commit script on
> there a few months ago.  After the upgrade, the router came up amnesiac,
> because the commit script has to be owned by root or a super-user.  It
> was owned by me (a super-user), but JUNOS wouldn't process the config to
> see that my UID existed and is a super-user.
>
> :facepalm:
>
> In other words, commit scripts (at least in python) must be owned by
> root if you want them to work after an upgrade, because no other user
> exists until after the script runs.  This seems like a shortcoming...
>
> --
> Chris Adams <cma at cmadams.net>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>