please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823871
Title:
After unattended-upgrade of
I can confirm this issue on 2 of our VMs running Ubuntu 18.04.
Today I lost a secondary IP on one of the interfaces, after unattended upgrades
installed a new systemd package.
Any updates on this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Same again today. I will need to create some countermeasure, e.g. after
every unattended upgrade a script that brings down and up the
interfaces, otherwise I will not be able to keep my services
availability. Kind of disappointed in this, but at least it will be a
solution.
--
You received this b
Today the same issue happened again. After systemd update my server
became unavailable...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823871
Title:
After unattended-upgrade of systemd IP configur
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823871
Title:
After u
Got same thing, but not on all virtual machines.
** Attachment added: "netplan.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+attachment/5258426/+files/netplan.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Is the information provided already enough to change this report's status? I
think we have provided details, as well as offered to give even more (thank you
Joi!) if required, so it would be great to follow up on this.
Thanks!
--
You received this bug notification because you are a member of Ub
I've done some more digging into the systemd package update issue. We
have a number of Ubuntu 18.04 hosts, most of them are virtual machines
running simple eth0 configurations under Hyper-V. All of those VMs
updated the systemd package without issue. The only hosts which had
issues after the sys
I followed up with my coworker who originally built our two misbehaving
boxes. He also ended up having to reboot the second box I left for him,
to get the br01 bridge configuration back in working order. Simply
running 'netplan apply' and restarting the systemd network service did
not resolve it,
I have followed the instructions in the /etc/network/interfaces file to
ditch netplan and use ifupdown:
# To re-enable ifupdown on this system, you can run:
#sudo apt install ifupdown
As an extra measure I have removed netplan packages completely:
~# grep netplan .bash_history
apt remove npl
> I statically configure the IP address using the interfaces file.
you mention the interfaces file, but this bug is against systemd - what
mechanism are you using to configure your network? For a fresh install
of 18.04, you will get netplan by default, using systemd-networkd as its
backend; is th
Two of our Ubuntu 18.04 hosts applied this update this morning and both
dropped offline. They're both using netplan and have bonded interfaces.
The bond layer was offline. I had to reboot to get the network stack
running again. I left one host offline so the coworker who configured
them can look
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823871
Title:
Af
13 matches
Mail list logo
