Public bug reported:
[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)
** Affects: zsys (Ubuntu)
Importance: Undecided
Status: New
** Affects: zsys (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: zsys (Ubuntu Bionic)
Importance: Undecided
Status: New
** Description changed:
[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.
+ * 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.
- * 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 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)
+ [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)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897563
Title:
Zsys changes the canmount property of persistent bpool/grub dataset
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1897563/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
