Regression in "lxd init" behavior in 2.0.11

Bug #1737020 reported by Stéphane Graber on 2017-12-07
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxd (Ubuntu)
Undecided
Unassigned
Xenial
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.

Stéphane Graber (stgraber) wrote :

Oh and it goes without saying that our manual testing plan got updated to better cover lxd init moving forward.

Changed in lxd (Ubuntu):
status: New → Triaged
status: Triaged → Invalid
Changed in lxd (Ubuntu Xenial):
status: New → Triaged
importance: Undecided → Critical

Hello Stéphane, or anyone else affected,

Accepted lxd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxd/2.0.11-0ubuntu1~16.04.3 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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/PerformingSRUVerification . Thank you in advance!

Changed in lxd (Ubuntu Xenial):
status: Triaged → Fix Committed
tags: added: verification-needed verification-needed-xenial
Stéphane Graber (stgraber) wrote :

Noticed another issue when using the "dir" backend, an unrelated warning about missing profile is shown. I uploaded a follow-up upload to fix that too (fix is upstream and jenkins is happy).

Using this same bug to track this.

Brian Murray (brian-murray) wrote :

Hello Stéphane, or anyone else affected,

Accepted lxd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxd/2.0.11-0ubuntu1~16.04.4 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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/PerformingSRUVerification . Thank you in advance!

Stéphane Graber (stgraber) wrote :

Confirmed all 3 fixes:
 - Running with dir backend doesn't show a warning anymore
 - Running with zfs backend asks for the pool name, uses the right default value and leads to a working pool
 - All runs now ask about network configuration

tags: added: verification-done verification-done-xenial
removed: verification-needed verification-needed-xenial
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lxd - 2.0.11-0ubuntu1~16.04.4

---------------
lxd (2.0.11-0ubuntu1~16.04.4) xenial; urgency=medium

  * Fix another regression in "lxd init":
    - When using the "dir" backend a unrelated profile warning was shown

lxd (2.0.11-0ubuntu1~16.04.3) xenial; urgency=medium

  * Fix two regressions in "lxd init" (LP: #1737020):
    - Missing question for ZFS pool name (when creating new one)
    - Missing LXD bridge questions

 -- Stéphane Graber <email address hidden> Thu, 07 Dec 2017 16:31:09 -0500

Changed in lxd (Ubuntu Xenial):
status: Fix Committed → Fix Released

The verification of the Stable Release Update for lxd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers