My preference would be to fix networkd, if that fails netplan, and isc-
dhcp only if there is syntax to online the device in the right l2/l3
state via kernel cmdline and that one needs to complete install over it.
For example, does automatic chzdev device enablement provides
autoconfiguration for hipersockets in l3? in that case it would be neat
for ip=dhcp to just do the right thing.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: netplan.io (Ubuntu)
Status: New => Confirmed
** Also affects: isc-dhcp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: isc-dhcp (Ubuntu)
Importance: Undecided => Low
** Changed in: isc-dhcp (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => Low
** Changed in: isc-dhcp (Ubuntu)
Importance: Low => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914740
Title:
IPs are not assigned for Hipersockets in DHCP mode
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
