Description of problem: When network services (e.g. dnsmasq, apache, etc) are configured to bind a secondary IP address, they will fail to start because systemd does not wait for the secondary IPs to be configured. Version-Release number of selected component (if applicable): systemd-230-6.mga6 How reproducible: Always Steps to Reproduce: 1. Add a secondary IP to one of your network interfaces 2. Configure a network service (e.g. dnsmasq) to bind only that IP. 3. Reboot the system and check the failed service.
Assigning to the registered systemd maintainer.
CC: (none) => marja11Assignee: bugsquad => mageia
@ Colin Sorry, but BugSquad decided to reassign this bug to the basesystem maintainers, even if you're the registered maintainer and even if you're not a member of the matching mailing list. The reason is that you're seldom around, nowadays. Please don't feel offended (well, you probably won't, since you're not the kind of guy to feel offended easily ;-) ). Please do feel invited to join https://ml.mageia.org/l/info/basesystem and the matching group https://wiki.mageia.org/en/Maintainer_groups (the latter after the wiki gets unlocked).
Assignee: mageia => basesystemCC: (none) => mageia
(In reply to Herbert Poetzl from comment #0) > 1. Add a secondary IP to one of your network interfaces How did you add that in particular? And you might need to add some more details about whether you use the default net_applet (which I believe does not allow to configure aliases) or networkmanager or ... ?
CC: (none) => doktor5000