Regression in "lxd init" behavior in 2.0.11
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Critical
|
Unassigned |
Bug Description
This is an SRU tracking bug for the fixes to two "lxd init" regressions in LXD 2.0.11.
1) Missing question about the ZFS pool name when creating a new pool.
2) Missing question about the LXD bridge configuration.
Both of those are part of our interactive workflow so didn't trip our automated testing and unfortunately didn't trip our manual testing either as were mostly focused on upgrades rather than validating that the initial configuration tool was asking all the expected questions.
This SRU should be rushed as those two issues make the initial configuration of LXD inconsistent with documentation and quite a bit harder for users to do.
# Testcase
Install LXD 2.0.11 on a clean system, run "lxd init", select "zfs" as the storage backend and accept to create a new pool. Confirm that you get asked for the pool name. Then later, check that you're asked to configure the LXD bridge and that answering yes causes a set of debconf prompts to show up.
# Regression potential
This only applies to new installations and has been manually tested already alongside the old LXD 2.0.10 to confirm that the behavior is now identical.
There is the possibility that we missed another regression in that code, but this fix would still be a good improvement.
Oh and it goes without saying that our manual testing plan got updated to better cover lxd init moving forward.