This bug was fixed in the package ifupdown - 0.8.36+nmu1ubuntu3.1

---------------
ifupdown (0.8.36+nmu1ubuntu3.1) jammy; urgency=medium

  [ Uwe Kleine-König ]
  * Fix if-up.d/resolved hook to properly work with nameservers and search
    domains (LP: #1981103)

  [ Heinrich Schuchardt ]
  *  Remove invalid lines from resolved integration scripts (LP: #1907878)

 -- Joao Andre Simioni <[email protected]>  Mon, 16 Oct 2023
14:41:24 +0000

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

-- 
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 Released

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     : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to