Sorry, Eoan is EOL in just a few weeks, and I don't think this will make
it. please upgrade to Focal if still affected by this bug.
** Changed in: systemd (Ubuntu Eoan)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
thanks, per comment 12 marking fixed in focal.
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => Fix Released
** Changed in: systemd (Ubuntu Focal)
Assignee: Dan Streetman (ddstreet) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Tried with image ubuntu-minimal-2004-focal-v20200501 (systemd
245.4-4ubuntu3). No issues seen. I will then upgrade our project to
Focal, which also has LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also I marked this as fix released upstream (per comment 8), and assume
this is fixed for Groovy as well (or, will be fixed during Groovy dev
cycle), but I did not specifically check Groovy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
> 245.5-2upstream202005091618~ubuntu19.10.1 from your ppa seems to be
fine:
ah, that's excellent, then, I'll try to find the upstream patch fixing
this.
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Eoan)
Importance:
I marked this as affecting Eoan, but I may not be able to get to
patching it before it reaches EOL, since that's in just 2 months. If
you do happen to upgrade to Focal, and find it's fixed there, please add
a comment.
--
You received this bug notification because you are a member of Ubuntu
245.5-2upstream202005091618~ubuntu19.10.1 from your ppa seems to be fine:
May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26):
REQUEST (renewing)
May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): ACK
May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP
For testing with the latest upstream, can you try the systemd from this ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/systemd-upstream
You should only use that for testing, please - remove it and revert the
packages back to the official versions once you've tested.
Also, strictly as a
Do you have any suggestion on what to look at?
Systemd only tracks bugs for the two most recently released versions (which
should be 245 and 244) and I don't have the ressources to test those.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
it looks like your dhcp lease is expiring, which causes networkd to drop
your dhcp configuration, including resetting your mtu back to its
original value. That's done asynchronously by netlink, and networkd
sets a flag "setting_mtu" while the netlink request to change the mtu is
pending.
After the weekend, I observed that the original MTU gets set on every second
renew:
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Saved original MTU: 1420
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1460
Apr 23 21:50:59 ct-prod systemd-networkd[1737]: ens4: Setting
This is the full log:
Apr 23 09:51:00 ct-prod systemd[1]: Stopping Network Service...
Apr 23 09:51:00 ct-prod systemd[1]: systemd-networkd.service: Succeeded.
Apr 23 09:51:00 ct-prod systemd[1]: Stopped Network Service.
Apr 23 09:51:00 ct-prod systemd[1]: Starting Network Service...
Apr 23
> 09:51:00 ens4: Configured
> 21:50:59 ens4: DHCP lease lost
er, did you happen to trim a few lines between those? Can you please
provide the full unedited log?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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/1874661
Title:
14 matches
Mail list logo
