Mailing List Archive: JUNOS upgrade annoyance...

JUNOS upgrade annoyance...

Aug 1, 2019, 5:58 AM

Post #1 of 3 (506 views)

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@cmadams.net>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: JUNOS upgrade annoyance... [ In reply to ]

melchior at aelmans

Aug 1, 2019, 7:45 AM

Post #2 of 3 (506 views)

Permalink

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@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@cmadams.net>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: JUNOS upgrade annoyance... [ In reply to ]

cra at wpi

Aug 1, 2019, 1:03 PM

Post #3 of 3 (504 views)

Permalink

PR. It is a bug for a valid config to not work after upgrade, unless the validate procedure catches it first. So they can either put this check into the validation stage, or chown the script during the upgrade.

On Thu, Aug 01, 2019 at 04:45:05PM +0200, Melchior Aelmans wrote:
> 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@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...
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp