[Bug 1863873] Re: Systemd fails to configure bridged network in LXC container

[Thomas Wien]

Thanks a lot for your explanations and workaround examples.

I expanded our ansible update playbooks to check if
/etc/netplan/10-lxc.yaml is installed, then to remove that file, runs
"netplan apply" and then remove the package "netplan.io". It seems to
work in our environment, without loosing the network configuration while
updating and also after reboot.

Here is the ansible section we tested. Maybe it is helpful to anyone
else. This script comes with no warranty and should be tested in your
environment thoroughly.

- name: Is Netplan configuring LXC?
  stat:
path: /etc/netplan/10-lxc.yaml
  register: netplan
- name: Remove networkd/netplan configuration
  file:
path: /etc/netplan/10-lxc.yaml
state: absent
  when: "netplan.stat.exists == true and ansible_virtualization_type == 'lxc'"
- name: Reload networkd/netplan
  command: netplan apply
  when: "netplan.stat.exists == true and ansible_virtualization_type == 'lxc'"
- name: Remove netplan.io
  apt:
name: netplan.io
state: absent
  when: "netplan.stat.exists == true and ansible_virtualization_type == 'lxc'"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863873

Title:
  Systemd fails to configure bridged network in LXC container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1863873] Re: Systemd fails to configure bridged network in LXC container

[Thomas Wien]

I can confirm this behavior after update to systemd 237-3ubuntu10.39 on
privileged and unprivileged containers. We classify this bug as critical
because in the next monthly update cycle via ansible orchestration we
would expect failing all Bionic LXC containers. The only workaround
seems to manually define a static network configuration in
/etc/netplan/10-lxc.yaml via lxc-attach. But this is not an acceptable
solution for 180 servers we run.

Some our Plesk servers already failed completely due to automatic
upgrades Plesk triggered daily. Websites were down for hours until we
figured out the reason.

I would appreciate that someone solves this problem due to urgency.

Thank you in advance.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863873

Title:
  Systemd fails to configure bridged network in LXC container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs