[Bug 1880869] Re: Use persistent device name for vdevs

2020-07-02 Thread Launchpad Bug Tracker
This bug was fixed in the package ubiquity - 20.04.15.1 --- ubiquity (20.04.15.1) focal; urgency=medium [ Sebastien Bacher ] * debian/real-po: updated translations from launchpad, including strings from the new subpage for RST (LP: #1874103) [ Michael Hudson-Doyle ] *

[Bug 1880869] Re: Use persistent device name for vdevs

2020-06-25 Thread Jean-Baptiste Lallement
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880869 Title: Use persistent

[Bug 1880869] Re: Use persistent device name for vdevs

2020-06-25 Thread Jean-Baptiste Lallement
SRU verification for Focal: I have reproduced the problem with ubiquity 20.04.15 in focal and have verified that the version of ubiquity 20.04.15.1 in -proposed fixes the issue. Marking as verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1880869] Re: Use persistent device name for vdevs

2020-06-24 Thread Brian Murray
Hello Jean-Baptiste, or anyone else affected, Accepted ubiquity into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubiquity/20.04.15.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1880869] Re: Use persistent device name for vdevs

2020-06-24 Thread Jean-Baptiste Lallement
** Description changed: [Impact]  * ZFS pools were created with device names such as /dev/sdX, /dev/vdX,... However, these names are not stable and may change on each reboot, leading to an unbootable system. - * "zpool create" now uses persistent device names with PARTUUID +  *

[Bug 1880869] Re: Use persistent device name for vdevs

2020-06-24 Thread Jean-Baptiste Lallement
** Description changed: [Impact] - * An explanation of the effects of the bug on users and +  * ZFS pools were created with device names such as /dev/sdX, + /dev/vdX,... However, these names are not stable and may change on each + reboot, leading to an unbootable system. - *

[Bug 1880869] Re: Use persistent device name for vdevs

2020-06-24 Thread Jean-Baptiste Lallement
** Also affects: ubiquity (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ubiquity (Ubuntu Focal) Status: New => Triaged ** Changed in: ubiquity (Ubuntu Focal) Importance: Undecided => High -- You received this bug notification because you are a member of

[Bug 1880869] Re: Use persistent device name for vdevs

2020-06-16 Thread Launchpad Bug Tracker
** Merge proposal linked: https://code.launchpad.net/~xnox/ubiquity/+git/ubiquity/+merge/385805 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880869 Title: Use persistent device name for vdevs

[Bug 1880869] Re: Use persistent device name for vdevs

2020-06-16 Thread Dimitri John Ledkov
** Description changed: + [Impact] + + * An explanation of the effects of the bug on users and + + * justification for backporting the fix to the stable release. + + * In addition, it is helpful, but not required, to include an +explanation of how the upload fixes this bug. + + [Test

[Bug 1880869] Re: Use persistent device name for vdevs

2020-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package ubiquity - 20.10.2 --- ubiquity (20.10.2) groovy; urgency=medium [ Jean-Baptiste Lallement ] * zsys-setup: Use persistent device name for vdevs (LP: #1880869) * Only export pools created during installation and containing dataset mounted

[Bug 1880869] Re: Use persistent device name for vdevs

2020-05-30 Thread Nicolay Doytchev
Re: SRUing I just got hit by this. I'm using a laptop that I added a second disk to. That changed the root disk from /dev/sda to /dev/sdb. The rpool got imported fine so boot succeeded. However silently bpool did not get imported. A couple of kernel updates were done over /boot inside rpool and

[Bug 1880869] Re: Use persistent device name for vdevs

2020-05-30 Thread Jean-Baptiste Lallement
Yes this is the plan together with several fixes and enhancements of zsys. The SRU work is in progress. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880869 Title: Use persistent device name for

[Bug 1880869] Re: Use persistent device name for vdevs

2020-05-29 Thread Brian Murray
Would this be worth SRU'ing into 20.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880869 Title: Use persistent device name for vdevs To manage notifications about this bug go to:

[Bug 1880869] Re: Use persistent device name for vdevs

2020-05-27 Thread Launchpad Bug Tracker
** Merge proposal linked: https://code.launchpad.net/~jibel/ubiquity/+git/ubiquity-1/+merge/384627 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880869 Title: Use persistent device name for

[Bug 1880869] Re: Use persistent device name for vdevs

2020-05-27 Thread Jean-Baptiste Lallement
** Description changed: - ZFS pools are currently created with device names. However, this name is not stable and may change. + ZFS pools are currently created with device names such as /dev/sdX, /dev/vdX,... However, this name is not stable and may change on each reboot. "zpool create" must