Branch: refs/heads/testing
Home: https://github.com/openSUSE/wicked
Commit: 8e7310c6637a403e9ecba64ad4af46f3963db43d
https://github.com/openSUSE/wicked/commit/8e7310c6637a403e9ecba64ad4af46f396...
Author: Jan Zerebecki
Date: 2020-01-31 (Fri, 31 Jan 2020)
Changed paths:
M etc/systemd/wickedd.service.in
Log Message:
-----------
Order wickedd After Open vSwitch on startup
Otherwise these are treading on each other while bringing up interfaces
which results in failures. Ordering Open vSwitch Before network.service
isn't suficient as wickedd and wickedd-nanny may start before that.
Commit: 17e60f2cce44b9ad267b3aed3b17b2808b133e23
https://github.com/openSUSE/wicked/commit/17e60f2cce44b9ad267b3aed3b17b2808b...
Author: Jan Zerebecki
Date: 2020-01-31 (Fri, 31 Jan 2020)
Changed paths:
M etc/systemd/wickedd-auto4.service.in
M etc/systemd/wickedd-dhcp4.service.in
M etc/systemd/wickedd-dhcp6.service.in
M etc/systemd/wickedd-nanny.service.in
M etc/systemd/wickedd.service.in
Log Message:
-----------
Order After network-pre on startup
Add network-pre.target where ordering is already After
SuSEfirewall2_init.service.
SuSEfirewall2_init.service is also missing a Before on network-pre.
After that is done in SuSEfirewall2 it can be removed here.
Quote about network-pre from man systemd.special:
This passive target unit may be pulled in by services that want to run
before any network is set up, for example for the purpose of setting up
a firewall. All network management software orders itself after this
target, but does not pull it in.
Compare: https://github.com/openSUSE/wicked/compare/6438e532edcf...17e60f2cce44