openresolv 3.17.0-1 breaks netctl unit startup if resolv.conf has immutable attribute set (upstream)
Description:
June 28 update of openresolv 3.16.5 -> 3.17.0
causes netctl
units to fail if openresolv cannot modify /etc/resolv.conf
. (bug filed upstream, link below)
Additional info:
- package version(s):
3.16.5
(fine)3.17.0
(netctl unit failure) - config and/or log files:
- link to upstream bug report, if any:
Relevant Journal Entries
Jun 29 00:44:58 valkyrie network[847]: resolvconf: signature mismatch: /etc/resolv.conf
Jun 29 00:44:58 valkyrie network[847]: resolvconf: run `resolvconf -u` to update
<snip>
Jun 29 00:44:59 valkyrie kernel: r8169 0000:05:00.0 enp5s0: Link is Down
Jun 29 00:44:59 valkyrie avahi-daemon[724]: Interface enp5s0.IPv4 no longer relevant for mDNS.
Jun 29 00:44:59 valkyrie systemd[1]: netctl@ethernet\x2dstatis\x2dvalkyrie.service: Main process exited, code=exited, status=1/FAILURE
Jun 29 00:44:59 valkyrie network[779]: Failed to bring the network up for profile 'ethernet-statis-valkyrie'
Jun 29 00:44:59 valkyrie avahi-daemon[724]: Leaving mDNS multicast group on interface enp5s0.IPv4 with address 192.168.6.14.
Jun 29 00:44:59 valkyrie systemd[1]: netctl@ethernet\x2dstatis\x2dvalkyrie.service: Failed with result 'exit-code'.
Jun 29 00:44:59 valkyrie avahi-daemon[724]: Withdrawing address record for 192.168.6.14 on enp5s0.
(full journal section in upstream bug report)
Upstream Bug Report
openresolv 3.17.0-1 breaks netctl unit startup if resolv.conf has immutable attribute set
Steps to reproduce:
- set immutable attribute on
/etc/resolv.conf
to prevent modification by extraneous resolver tools. (server with specific requirements) - create simple static IP from
/etc/netctl/example
directory. (configure to start at boot) - reboot - network interface is brought up correctly, but when openresolv can't modify
/etc/resolv.conf
it marks the serviceFAILED
taking down the network.
Extensive Thread on arch-general
The thread on arch-general containing all logs and configs is titled: "Updated on 25th to 6.15.3 + firmware (fine), update tonight to 6.15.4 + firmware, network not up, dhcpd4 fails?"
Will report back with updates from upstream.