** Changed in: zsys (Ubuntu Focal)
Assignee: (unassigned) => Didier Roche (didrocks)
** No longer affects: zsys (Ubuntu Bionic)
** 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 Desktop
Packages, which is subscribed to zsys in Ubuntu.
https://bugs.launchpad.net/bugs/1897563
Title:
Zsys changes the canmount property of persistent bpool/grub dataset
Status in zsys package in Ubuntu:
Fix Released
Status in zsys source package in Focal:
Fix Committed
Bug description:
[Impact]
* People having personal layout, like a persistent dedicated dataset under
/boot like /boot/grub will get it unmouted after a state revert.
* Side effects:
- those datasets are never marked as being part of the current machine, or
any state.
- bpool and bpool/BOOT are not listed in the unmanaged dataset list.
[Test Case]
* Install ZFS manually with a persistent bpool/bpool/grub dataset
* Take a snapshot
* Revert to this snapshot when rebooting
* Check that the persistent grub dataset is still mounted
* You can check as well with zsysctl show --full that you have this
persistent dataset attached to the machine.
[Regression Potential]
* New datasets under /boot could appear to be attached by the machine (even
if unlikely due to the huge testsuite which has been updated and checked)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1897563/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
