1871fbec7b
When the lxc-dnsmasq service is restarted while ipv6 is active, it will always fail to restart because the ip -6 addr add command fails due to the address already existing on the interface. ex. Apr 01 22:39:48 lsn-mc1009 systemd[1]: Starting lxc dnsmasq service... Apr 01 22:39:48 lsn-mc1009 lxc-system-manage[19134]: Creating LXC IPtables rules. Apr 01 22:39:48 lsn-mc1009 lxc-system-manage[19134]: RTNETLINK answers: File exists Apr 01 22:39:48 lsn-mc1009 systemd[1]: lxc-dnsmasq.service: Control process exited, code=exited status=2 Apr 01 22:39:48 lsn-mc1009 systemd[1]: Failed to start lxc dnsmasq service. Apr 01 22:39:48 lsn-mc1009 systemd[1]: lxc-dnsmasq.service: Unit entered failed state. Apr 01 22:39:48 lsn-mc1009 systemd[1]: lxc-dnsmasq.service: Failed with result 'exit-code'. Apr 01 22:39:50 lsn-mc1009 systemd[1]: lxc-dnsmasq.service: Service hold-off time over, scheduling restart. Change-Id: Ia3ebaf2125a00c4031f50bf03b60dd5659f9d660 |
||
---|---|---|
.. | ||
meta-data | ||
prep-scripts | ||
irqbalance.j2 | ||
lxc-dnsmasq-systemd-init.j2 | ||
lxc-image-fetch-url.py.j2 | ||
lxc-net-bridge.cfg.j2 | ||
lxc-net-redhat-bridge.cfg.j2 | ||
lxc-net-suse-bridge.cfg.j2 | ||
lxc-net-suse-routes.cfg.j2 | ||
lxc-net-suseredhat-postdown.cfg.j2 | ||
lxc-openstack.apparmor.j2 | ||
lxc-openstack.conf.j2 | ||
lxc-system-manage.j2 | ||
lxc.default.j2 | ||
sudoers.j2 | ||
systemd-machined.service.j2 | ||
systemd-proxy-unit.conf.j2 |