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 <stgra...@ubuntu.com> Thu, 07 Dec 2017 16:31:09
-0500
** Changed in: lxd (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1737020
Title:
Regression in "lxd init" behavior in 2.0.11
Status in lxd package in Ubuntu:
Invalid
Status in lxd source package in Xenial:
Fix Released
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1737020/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
