*** This bug is a duplicate of bug 1756846 ***
https://bugs.launchpad.net/bugs/1756846
Thanks to the investigation from Steve, it seems that during the dist-
upgrade process ifupdown was removed due a transient conflict during the
devel cycle. This caused it to be removed. It being removed did
As per cloud-init networking disabled. Please reopen task if you find
cloud-init is in the picture here.
** Changed in: cloud-init (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdo
Your config file is apparently named /etc/netplan/netplan.conf, which
does not match the required "*.yaml" pattern (which is documented in the
netplan(5) manpage and elsewhere).
** Changed in: netplan.io (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are
https://pastebin.ubuntu.com/p/YPRxSrjHZ9/
** Changed in: netplan.io (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1761294
Title:
> 3. Configured netplan and applied the config:
> 5. Interfaces dont get configured correctly:
Not sure what happened to 4 ;) But in any case, can you please confirm:
- what is the full set of config files under /etc/netplan after boot?
- what commands did you run to apply the config, and what wa
cloud-init-output.log after manually rebooting the machine.
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => New
** Attachment added: "cloud-init-output.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1761294/+attachment/5101804/+files/cloud-init-output.log
** A
6 matches
Mail list logo