NFS-based remote root hangs when running 'netplan apply'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
initramfs-tools (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Artful |
Won't Fix
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
netplan.io (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Invalid
|
Undecided
|
Unassigned | ||
Artful |
Invalid
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
nplan (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Artful |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Netboot users with a remote filesystem over NFS (possibly over other networked filesystems).
[Test cases]
1) Boot a system with its root filesystem over NFS.
2) Run 'sudo netplan apply'
3) Validate that the system remains responsive and keeps connectivity over the same IP address as it had.
[Regression potential]
This SRU changes network properties, and enforces that networkd does not release and re-request an IP address from DHCP when it is restarted. Environments relying on the IP release/renew behavior may find themselves staying on the previous IP address, which might negatively impact connectivity. Changes in connectivity on a system running netplan should be investigated as a potential regression from this SRU. Other regression possibilities would include failure to get a new IP address over time (usually seen as losing connectivity) or possible IP conflicts on a network.
---
With a system booted on the network, with its remote root fs on NFS:
Running 'netplan apply' restarts systemd-networkd, which releases the IP received from DHCP. With no IP (and and IP potentially changing), the NFS server can't be reached so the system hangs.
'netplan apply' or restarting systemd-networkd should not affect teh system, it should continue working normally despite "changing" network states, as long as the effective IP remains the same.
description: | updated |
Changed in nplan (Ubuntu): | |
status: | New → Invalid |
Changed in nplan (Ubuntu Bionic): | |
status: | New → Invalid |
Changed in netplan.io (Ubuntu Xenial): | |
status: | New → Invalid |
Changed in netplan.io (Ubuntu Artful): | |
status: | New → Invalid |
tags: | removed: verification-done-artful verification-done-bionic verification-done-xenial |
Changed in initramfs-tools (Ubuntu Artful): | |
status: | Fix Committed → Won't Fix |
Hello Mathieu, 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.36. 2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification- needed- bionic to verification- done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- bionic. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!