Hello Jacopo, or anyone else affected,

Accepted ifupdown into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ifupdown/0.8.36+nmu1ubuntu3.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ifupdown (Ubuntu Jammy)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1907878

Title:
  wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
  /etc/network/if-up.d/resolved: 12: mystatedir: not found)

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Jammy:
  Fix Committed

Bug description:
  Syslog error:

     nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir:
  not found

  I think it's because of this line:

    if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then
        mystatedir statedir ifindex interface             <------------- this 
is interpreted as a 'mystatedir' command and fails

        interface=$IFACE
        if [ ! "$interface" ]; then

  Perhaps the intention was to 'export mystatedir statedir ...'

  SRU for Jammy:

  [ Impact ]

     * /etc/network/if-{up,down}.d/resolved have a mistype:
     
     mystatedir statedir ifindex interface
     
     And when this line is executed, mystatedir is not found (not a valid 
command)
     and it generates an error log in /var/log/syslog and the terminal output. 
     It's not fatal, and the rest of the code gets executed, but it generates 
the
     message.
     
     # ifup ens3
     /etc/network/if-up.d/resolved: 12: mystatedir: not found

     # ifdown ens3
     /etc/network/if-down.d/resolved: 12: mystatedir: not found 
     
     The fix accepted in kinetic is only to remove this line. The same fix can 
be
     applied to Jammy.
     
  [ Test Plan ]

     With the new package installed, remove netplan configuration and add a 
valid
     /etc/network/interfaces file and then use the commands:
     
     # ifdown <interface>
     # ifup <interface>
     
     And confirm the messages are not displayed and the network configuration
     succeeds.
     
  [ Where problems could occur ]

     If mystatedir would be a valid command or function, which is not the case,
     that could break the script.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to