According to the reporter, this issue was not observed in Ubuntu 21.04
forward. I do not think there is a strong case for addressing this in
focal or bionic.
** Changed in: systemd (Ubuntu Bionic)
Status: Incomplete => Won't Fix
** Changed in: systemd (Ubuntu Focal)
Status:
The attachment "sd-netlink-make-timeout-message-sealed.patch" seems to
be a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a
** Patch added: "sd-netlink-make-timeout-message-sealed.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930738/+attachment/5518731/+files/sd-netlink-make-timeout-message-sealed.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: systemd (Ubuntu Focal)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Focal)
Importance: Low => Undecided
** Changed in: systemd (Ubuntu Bionic)
Importance: Low => Undecided
--
You received this bug notification because you are a
Hi, Sorry for the late reply I didn't receive the notifications.
This problem happens on a "bare" environment: it's a simple server (IPv6
RA + v4 DHCP) with some IPv6 ranges assigned to the `lo` interface.
Don't hesitate if you need more info, although we don't reproduce the
bug anymore due to
> There are more details regarding this issue and may be commit refs at
> https://github.com/systemd/systemd/issues/17012
I'm aware of that as noted in my updates to the description, but that
doesn't actually fix this inside unprivileged containers, which is the
only place I can reproduce this.
I got this issue on a VPS from cloud provider. For me, this issue occurs
every time I restart the VPS. To access the server after restart, I
execute `netplan apply` command using web console/KVM.
Furthermore, this issue does not occurs in Ubuntu 21.04
There are more details regarding this issue
** Attachment added: "10-test.yaml"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930738/+attachment/5514117/+files/10-test.yaml
** Description changed:
[impact]
number of statically defined addresses for an interface in systemd-
networkd is limited
[test case]
Deepika, Frank, is this happening for you inside an unprivileged
container, or some other environment?
I'm able to reproduce this in a container, but it appears still broken
with upstream systemd, so I'm confused by Frank's comment 2. Also, it
isn't intermittent at all for me, so maybe you're
** Description changed:
[impact]
number of statically defined addresses for an interface in systemd-
networkd is limited
[test case]
Note: this only occurs in a container; this is not reproducable in a VM
or bare metal.
Configure netplan with the attached yaml file (TBD:
** Description changed:
[impact]
number of statically defined addresses for an interface in systemd-
networkd is limited
[test case]
Note: this only occurs in a container; this is not reproducable in a VM
or bare metal.
Configure netplan with the attached yaml file (TBD:
** Description changed:
+ [impact]
+
+ number of statically defined addresses for an interface in systemd-
+ networkd is limited
+
+ [test case]
+
+ Note: this only occurs in a container; this is not reproducable in a VM
+ or bare metal.
+
+ Configure netplan with the attached yaml file (TBD:
From fresh installation of ubuntu, I simply configured one main and 255
IPv4 address from /24 subnet as mentioned on original post in
/etc/netplan/10-ens3.yaml and this issue occurs. Even tried Ubuntu
20.04.2 LTS, same issue.
--
You received this bug notification because you are a member of
can you provide steps to reproduce the problem?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930738
Title:
network configuration failed on reboot
Status in systemd
Hi,
In our case a backport of the specific commit fixed the issue. I really
do think that this is (a rather difficult to reproduce) problem, which
the above commit fixes.
Cheers
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
i can't reproduce this, and your log output looks like you have are
having problems with your ipv6 configuration, not ipv4. you'll need to
attach the full journal log if you still have this problem
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug
16 matches
Mail list logo
