The working example seems to set a default route in the legacy way, using the
"gateway4" setting:
gateway4: 10.245.168.1
While the broken example sets a default route (on routing table 1 only) in the
new way, using the "routes" setting.
routes:
- table: 1
to: 0.0.0.0/0
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1951586
Title:
Need option to specify wifi regulatory domain
No, it was implemented & released upstream as of
https://github.com/canonical/netplan/pull/283 so the netplan project
task can be closed.
FYI: The work will still be backported to Jammy via LP: #1988447
** Changed in: netplan
Status: In Progress => Fix Released
--
You received this bug
** Also affects: netplan
Importance: Undecided
Status: New
** Changed in: netplan
Importance: Undecided => Wishlist
** Changed in: netplan
Status: New => Triaged
** Tags added: fr-2119
--
You received this bug notification because you are a member of Yahoo!
Engineering
Setting it to invalid for netplan as well. If there are any further
issues, feel free to re-open.
** Changed in: netplan
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1892851
Title:
Staged boot, to fix integration of systemd
Doing some experiments this seems to be working with netplan.io 0.100 in
Groovy. No matter if 'match.macaddress' is set or not on my local eth
interface.
As far as I can tell the fix was released with netplan 0.99 in Focal
final and was SRU'ed to Bionic as well.
** Changed in: netplan.io (Ubuntu Groovy)
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1898997
Title:
MAAS cannot deploy/boot if OVS bridge is
The netplan part is fixed in Groovy as of: netplan.io 0.100-0ubuntu5
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
The SSH failure seems to be related to cloud-init not detecting the OVS bridge
+ slaves correctly. Therefore, the cloud-init 'init' stage fails with an
exception:
"RuntimeError: Not all expected physical devices present: {'52:54:00:d9:08:1c'}"
I'm working on a pull request here:
We found a fix for this problem in netplan itself.
The overall idea of a staged-boot environment should probably still be
considered for a future release of cloud-init.
https://github.com/CanonicalLtd/netplan/pull/162
** Also affects: netplan
Importance: Undecided
Status: New
--
You
Public bug reported:
[Intro]
Cloud-init makes use of the "netplan" systemd generator, but calls "netplan
generate" manually at runtime, while currently executing the initial systemd
boot transaction, instead of running it as intended via "systemctl
daemon-reload" at systemd generator stage,
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1763608
Title:
Netplan ignores Interfaces without IP Addresses
Status
13 matches
Mail list logo
