Ubuntu 20.10 (Groovy Gorilla) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: dropbear (Ubuntu Groovy)
Status: Triaged => Won't Fix
--
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: initramfs-tools (Ubuntu Focal)
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/187688
Will there be a fix for this on focal too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876884
Title:
netplan using incorrect renderer
To manage notifications about this bug go to:
https://bugs.l
@vorlon
I see. Imho, we need to add API to configure "non-critical" internet.
Because for example, netboot in subiquity should be "non-critical" too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876
The initramfs-tools change is reasonable, but I disagree that the
dropbear behavior is "correct". The use of 'critical' for network
interfaces should be limited to those that actually need to be up for
the root filesystem to be available. Using dropbear for a one-time
unlock of the rootfs at boot
This bug was fixed in the package initramfs-tools - 0.136ubuntu8
---
initramfs-tools (0.136ubuntu8) groovy; urgency=medium
* Drop renderer from netplan yaml, such that netplan uses the default
rendered for the target system, i.e. NetworkManager on the
desktop. LP: #1876884
** Changed in: initramfs-tools (Ubuntu Groovy)
Status: New => 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/1876884
Title:
netplan using incorrect renderer
To manage notificati
I think what dropbear does is "right", and initramfs-tools should do the
right thing.
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: dropbear (Ubuntu Focal)
Status: New => Invalid
** Changed in: dropbear (Ubuntu Groovy)
Status:
alternative, we can drop the renderer setting, then it will be inherited
from the installed system.
or I guess we should reorder the file =/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876884
Titl
I feel like dropbear-initramfs should learn how to detect if one is on
desktop or not, and ensure renderer network-manager is used.
Or like make it a "non-critical" network connection, meaning that no
networking configuration is propagated to the host machine.
Howe important is it for you that ne
Any update on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876884
Title:
netplan using incorrect renderer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+so
I created a file
/etc/initramfs-tools/scripts/init-bottom/deconfigure-interfaces:
#!/bin/sh
rm -f /run/netplan/*
-
That works fine as a workaround! Flushing the device is not needed.
> IMO option (2) is actually a proper solution, this is why I am
assigning this bug to 'dropbear', as I thi
Hi Yannik,
I think you have two options:
1) Workaround by adding /etc/netplan/xxx.yaml (or any other name which
lexically sorts after "enp1s0.yaml"):
network:
version: 2
renderer: NetworkManager
ethernets:
enp1s0:
dhcp4: true
2) Cleanup dropbear-initramfs interfaces (as described
** Also affects: dropbear (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876884
Title:
netplan using incorrect renderer
To manage notifications
> How did you setup networking inside your initramfs? Apparently you did
not use the kernel CMDLINE, did you configure something inside /etc
/initramfs-tools/initramfs.conf instead?
I have not done any modifications at all to the initramfs or the kernel
cmdline except for installing dropbear-initr
After some more research, I found this "Ask Ubuntu" topic, where the
exact same problem is reported: https://askubuntu.com/questions/1228433
/what-is-creating-run-netplan-eth0-yaml
It seems like "initramfs-tools" is generating the
/run/netplan/enp1s0.yaml file, managed by the "system-dnetworkd"
re
dropbear-initramfs sounds interesting...
How did you setup networking inside your initramfs? Apparently you did not use
the kernel CMDLINE, did you configure something inside
/etc/initramfs-tools/initramfs.conf instead?
--
You received this bug notification because you are a member of Ubuntu
Bu
** Tags added: id-5eb42dd47e87c9618cd3a3be
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876884
Title:
netplan using incorrect renderer
To manage notifications about this bug go to:
https://bugs.l
What is your /proc/cmdline ?
---
$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/vgubuntu-root ro quiet
splash vt.handoff=7
Do you have `ip=` there? what is it?
---
No ip= option as you can see above.
It feels like you are booting with `ip=dhcp` set on t
** Also affects: netplan.io (Ubuntu Groovy)
Importance: High
Status: New
** Also affects: netplan.io (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu Focal)
Importance: Undecided => High
** Tags removed: rls-ff-incoming
--
You received t
What is your /proc/cmdline ?
Do you have `ip=` there? what is it?
It feels like you are booting with `ip=dhcp` set on the kernel
commandline, when you do that, we bring netwokring up in the initramfs,
and generate netplan.yaml for it.
Can you please confirm if you have any /run/netplan/*.yaml fi
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => High
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876884
Title:
netplan using incorrect renderer
To
** Summary changed:
- eth connection 'unmanaged' when using netplan
+ netplan using incorrect renderer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876884
Title:
netplan using incorrect renderer
23 matches
Mail list logo