Won't Fix for nplan: we will not be backporting these fixes to releases
prior to 18.04.
** Changed in: nplan (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
* tests/integra
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed: verification-needed
Installing 0.40.1~18.04.3 from bionic-proposed fixed this issue for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736975
Title:
netplan does not bring up anonymous bridge on boot
To manage not
Hello Colin, or anyone else affected,
Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.40.1~18.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
** Changed in: netplan.io (Ubuntu Bionic)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736975
Title:
netplan does not bring up anonymous bridge on boot
This bug was fixed in the package netplan.io - 0.40.1~18.04.2
---
netplan.io (0.40.1~18.04.2) bionic; urgency=medium
* Fix typo breaking rename on 'netplan apply'. (LP: #1770082)
netplan.io (0.40.1~18.04.1) bionic; urgency=medium
* Backport netplan 0.40.1 to 18.04. (LP: #1793309
Verification-done with netplan.io 0.40.1~18.04.2 on bionic:
I have verified that with dhcp4: no, dhcp6: no, accept-ra: no on the
bridge interface and not static addresses set, the interface is brought
up correctly by networkd.
root@working-guinea:~# cat /etc/netplan/50-cloud-init.yaml
network:
Hello Colin, or anyone else affected,
Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.40.1~18.04.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
ubuntu@new-man:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.40.1~18.04.1 amd64 YAML network configuration abstraction for
various backends
I have reverified this SRU using Trevor's netplan yaml. The bridge
interface is correctly brought up at boot, and the right addresses are
set to the right
Hello Colin, or anyone else affected,
Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.40.1~18.04.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
I can also confirm that the new package (from the proposed archive) now
allows the bridge interface to come up at boot.
My new package (apt list netplan.io): netplan.io/bionic-proposed,now
0.40~18.04.1 amd64 [installed]
My netplan config:
network:
version: 2
renderer: networkd
etherne
I have tested the package in proposed and it solved the issue; there is
now a 2nd systemd file generated in /run/systemd/network called .network (same as in the workaround). The bridge is now
automatically brought up, also after a reboot.
** Tags removed: verification-needed-bionic
** Tags added:
Hello Colin, or anyone else affected,
Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.40~18.04.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
** Description changed:
+ [Impact]
+ Netplan users setting up bridges.
+
+ [Test cases]
+ 1) Add a new bridge configuration in netplan yaml, without an IP address set:
+
+ [...]
+ bridges:
+ br0:
+ interfaces: [ interface ]
+ dhcp4: false
+ parameters:
+ stp:
** Changed in: netplan
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736975
Title:
netplan does not bring up anonymous bridge on boot
To manage notificat
> How can I make this bridge come up at boot without assigning an IP
address?
See the link earlier in this thread:
http://djanotes.blogspot.com/2018/04/anonymous-bridges-in-netplan.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am running the latest version of Ubuntu 18.04 as a KVM hypervisor with
multiple bridges. My bridges are down after reboot as described in this
bug. Enabling DHCP does make the bridge come up, but I only need layer 2
on the bridges and I don't want an IP. I'm assuming assigning an IP will
also wor
this is still broken in bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736975
Title:
netplan does not bring up anonymous bridge on boot
To manage notifications about this bug go to:
https:/
I just tested netplan 0.39 on a 18.04 VM and it does not fix the
problem, the bridge is still DOWN upon creation :-(
netplan
network:
version: 2
bridges:
br0:
dhcp4: false
addresses:
- 10.10.10.254/24
parameters:
stp: false
I had just filed bug #1782155, which may be a duplicate of this one.
Adding 'accept-ra: no' does not work around the issue for me.
I'm happy to test the newer version of Netplan though; is it available
in a PPA pending SRU?
--
You received this bug notification because you are a member of Ubunt
will this new version be available via bionic-updates ?
or will the fix be back-ported to 0.36.x ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736975
Title:
netplan does not bring up anonymous br
This bug was fixed in the package netplan.io - 0.39
---
netplan.io (0.39) cosmic; urgency=medium
* New upstream release:
- Allow link-local addresses to be configured. (LP: #1771704)
- Forces bridges with no addresses to be brought online. (LP: #1736975)
-- Mathieu Trudel-
I an using Ubuntu Server as a KVM-host, relying on multiple anonymous
bridges, and am suffering from this bug under 18.04.
For others needing a workaround: I do configure the bridges with
netplan.io as usual and bring up the bridges by defining in file
/etc/systemd/network/10-netplan-brUp.network
https://github.com/CanonicalLtd/netplan/tree/carrier has a potential fix
now. I'll test it some more and check some corner-cases where it might
break, and release with that soonish.
** Also affects: netplan
Importance: Undecided
Status: New
** Changed in: netplan
Status: New => I
Can confirm - adding accept-ra still doesn't bring up the bridge.
Nplan Version: 0.36.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736975
Title:
netplan does not bring up anonymous bridge on bo
Adding "accept-ra" to the netplan YAML for the bridge is not sufficient
to make the bridge come up, at least with 18.04 updated as of 19 April
2018.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/173697
In this case you may set:
accept-ra: no
In your netplan YAML; this will at least set IPv6AcceptRA=no, which
should be sufficient for the bridge to come up, and is already available
in netplan 0.34.1 (in Ubuntu 18.04)
Controlling LinkLocalAddressing= will remain as a TODO.
** Changed in: nplan
I've figured out how to work around this. It's all documented at
http://djanotes.blogspot.com/2018/04/anonymous-bridges-in-netplan.html.
In short, I tell systemd-networkd directly to bring up the bridge. To do
this, in addition to the rest of the configuration in netplan, I create
/etc/systemd/net
You might be able to work around this by setting the ip to 0.0.0.0/32.
However, when tested that it seem to DHCP assign an ipv6 address, which
I assume is another bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Additionally, this is still a bug in Ubuntu 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736975
Title:
netplan does not bring up anonymous bridge on boot
To manage notifications about this
This is going to be a particular nuisance for those hosting Xen farms
with Ubuntu as Dom0.
Considering Ubuntu 17.10 is the only distro I found supporting a lete-
enough Xen build for my purposes, “out of the box”, the two reports
including mine are probably an “iceberg tip”.
I am presently seekin
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nplan (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/1736975
Title:
netp
33 matches
Mail list logo
