Public bug reported:
When I configured multiple ports using/etc/network/interfaces which have
“auto”, I noticed that [email protected] was executed before networking.service,
and [email protected] relied on the script ifupdown-hotplug, which caused the
address of the port configuration entry to be configured twice at boot time.
① udev -> ifupdown-hotplug -> [email protected] -> ifup "interface name"
② networking.service -> ifup -a
This causes networking.service to fail, with one of the portals reporting the
error RTNL file exists. This problem only exists when configuring multiple
portals, and disappears when I use systemctl disable networking.
I suspect that the script of hotplug uses systemctl start “--no-block to start
[email protected]”, which causes competition with networking.service。Because in the
end, the configuration in/etc/networking/interfaces is done correctly
** Affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
** Tags: ifupdown
--
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/2115464
Title:
ifup.service makes networking.service failed
Status in ifupdown package in Ubuntu:
New
Bug description:
When I configured multiple ports using/etc/network/interfaces which have
“auto”, I noticed that [email protected] was executed before networking.service,
and [email protected] relied on the script ifupdown-hotplug, which caused the
address of the port configuration entry to be configured twice at boot time.
① udev -> ifupdown-hotplug -> [email protected] -> ifup "interface name"
② networking.service -> ifup -a
This causes networking.service to fail, with one of the portals reporting the
error RTNL file exists. This problem only exists when configuring multiple
portals, and disappears when I use systemctl disable networking.
I suspect that the script of hotplug uses systemctl start “--no-block to
start [email protected]”, which causes competition with networking.service。Because
in the end, the configuration in/etc/networking/interfaces is done correctly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2115464/+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
