2020-06-01 07:45:31 |
Didier Roche-Tolomelli |
bug |
|
|
added bug |
2020-06-01 07:46:27 |
Didier Roche-Tolomelli |
description |
This was reported as https://github.com/ubuntu/zsys/issues/103. |
This was reported as https://github.com/ubuntu/zsys/issues/103.
Don’t remove anything that is under /USERDATA/ if this wasn’t a fully zsys unlinked user state (with every other states unlinked as well) |
|
2020-06-03 00:38:52 |
Launchpad Janitor |
zsys (Ubuntu): status |
New |
Fix Released |
|
2020-06-09 08:29:12 |
Didier Roche-Tolomelli |
description |
This was reported as https://github.com/ubuntu/zsys/issues/103.
Don’t remove anything that is under /USERDATA/ if this wasn’t a fully zsys unlinked user state (with every other states unlinked as well) |
[Impact]
* People creating manually datasets under the reserved namespace /USERDATA/ were considered good to clean up by ZSys and were removed.
* Even if this namespace shouldn’t be used by user, mitigate by preventing GC to collect and destroy them.
* Mark them differently to ZSys user datasets that were untagged so that those last ones are still considered for cleanup
* This is covered by dedicated use cases.
[Test Case]
1. zfs create rpool/USERDATA/foo
2. Run zsysctl service GC
3. Check that rpool/USERDATA/foo hasn’t been collected.
[Regression Potential]
* The clean up was too extreme for those edge cases users.
* GC is a separate, timer-based process and don’t impact boot or other operations.
* The 30 existing tests on the GC didn’t regress and we now have some additional ones around those use case.
This was reported as https://github.com/ubuntu/zsys/issues/103.
Don’t remove anything that is under /USERDATA/ if this wasn’t a fully zsys unlinked user state (with every other states unlinked as well) |
|
2020-06-09 08:29:20 |
Didier Roche-Tolomelli |
description |
[Impact]
* People creating manually datasets under the reserved namespace /USERDATA/ were considered good to clean up by ZSys and were removed.
* Even if this namespace shouldn’t be used by user, mitigate by preventing GC to collect and destroy them.
* Mark them differently to ZSys user datasets that were untagged so that those last ones are still considered for cleanup
* This is covered by dedicated use cases.
[Test Case]
1. zfs create rpool/USERDATA/foo
2. Run zsysctl service GC
3. Check that rpool/USERDATA/foo hasn’t been collected.
[Regression Potential]
* The clean up was too extreme for those edge cases users.
* GC is a separate, timer-based process and don’t impact boot or other operations.
* The 30 existing tests on the GC didn’t regress and we now have some additional ones around those use case.
This was reported as https://github.com/ubuntu/zsys/issues/103.
Don’t remove anything that is under /USERDATA/ if this wasn’t a fully zsys unlinked user state (with every other states unlinked as well) |
[Impact]
* People creating manually datasets under the reserved namespace /USERDATA/ were considered good to clean up by ZSys and were removed.
* Even if this namespace shouldn’t be used by user, mitigate by preventing GC to collect and destroy them.
* Mark them differently to ZSys user datasets that were untagged so that those last ones are still considered for cleanup
* This is covered by dedicated use cases.
[Test Case]
1. zfs create rpool/USERDATA/foo
2. Run zsysctl service GC
3. Check that rpool/USERDATA/foo hasn’t been collected.
[Regression Potential]
* The clean up was too extreme for those edge cases users.
* GC is a separate, timer-based process and don’t impact boot or other operations.
* The 30 existing tests on the GC didn’t regress and we now have some additional ones around those use case.
-----
This was reported as https://github.com/ubuntu/zsys/issues/103.
Don’t remove anything that is under /USERDATA/ if this wasn’t a fully zsys unlinked user state (with every other states unlinked as well) |
|
2020-06-09 08:29:23 |
Didier Roche-Tolomelli |
zsys (Ubuntu): assignee |
|
Didier Roche (didrocks) |
|
2020-06-09 08:29:25 |
Didier Roche-Tolomelli |
zsys (Ubuntu): importance |
Undecided |
High |
|
2020-06-09 08:29:31 |
Didier Roche-Tolomelli |
nominated for series |
|
Ubuntu Focal |
|
2020-06-09 08:29:31 |
Didier Roche-Tolomelli |
bug task added |
|
zsys (Ubuntu Focal) |
|
2020-06-09 08:29:39 |
Didier Roche-Tolomelli |
zsys (Ubuntu Focal): assignee |
|
Didier Roche (didrocks) |
|
2020-06-09 08:29:41 |
Didier Roche-Tolomelli |
zsys (Ubuntu Focal): importance |
Undecided |
High |
|
2020-06-19 06:37:38 |
Timo Aaltonen |
zsys (Ubuntu Focal): status |
New |
Fix Committed |
|
2020-06-19 06:37:39 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2020-06-19 06:37:42 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
2020-06-19 06:37:45 |
Timo Aaltonen |
tags |
|
verification-needed verification-needed-focal |
|
2020-06-24 12:42:07 |
Jean-Baptiste Lallement |
tags |
verification-needed verification-needed-focal |
verification-done verification-done-focal |
|
2020-07-02 08:29:32 |
Launchpad Janitor |
zsys (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
2020-07-02 08:30:22 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|