| 2020-04-01 08:37:46 |
Didier Roche-Tolomelli |
bug |
|
|
added bug |
| 2020-04-01 08:38:01 |
Didier Roche-Tolomelli |
description |
Run that as part of GC so that we can clean them up later |
Untag them as part of GC so that we can clean them up later |
|
| 2020-04-07 13:14:38 |
Didier Roche-Tolomelli |
description |
Untag them as part of GC so that we can clean them up later |
Ideally, we would untag them as part of GC so that we can clean them up later. However, those can be linked to states on other pools with same pool name than targetted one, and it will be hard to match them.
Give a command for users to see them in status and then manually remove suspicious datasets ? |
|
| 2020-04-07 13:17:02 |
Jean-Baptiste Lallement |
zsys (Ubuntu): status |
New |
Triaged |
|
| 2020-04-07 13:17:06 |
Jean-Baptiste Lallement |
zsys (Ubuntu): importance |
Undecided |
Medium |
|
| 2020-06-01 07:33:27 |
Didier Roche-Tolomelli |
summary |
Collect unmatched bootfs-datasets on all userdata |
Collect deleted users |
|
| 2020-06-01 07:33:34 |
Didier Roche-Tolomelli |
bug task added |
|
shadow (Ubuntu) |
|
| 2020-06-03 00:38:52 |
Launchpad Janitor |
zsys (Ubuntu): status |
Triaged |
Fix Released |
|
| 2020-06-09 08:31:16 |
Didier Roche-Tolomelli |
shadow (Ubuntu): importance |
Undecided |
Medium |
|
| 2020-06-09 08:31:20 |
Didier Roche-Tolomelli |
shadow (Ubuntu): assignee |
|
Didier Roche (didrocks) |
|
| 2020-06-09 08:31:22 |
Didier Roche-Tolomelli |
zsys (Ubuntu): assignee |
|
Didier Roche (didrocks) |
|
| 2020-06-09 08:31:28 |
Didier Roche-Tolomelli |
nominated for series |
|
Ubuntu Focal |
|
| 2020-06-09 08:31:28 |
Didier Roche-Tolomelli |
bug task added |
|
shadow (Ubuntu Focal) |
|
| 2020-06-09 08:31:28 |
Didier Roche-Tolomelli |
bug task added |
|
zsys (Ubuntu Focal) |
|
| 2020-06-09 08:31:42 |
Didier Roche-Tolomelli |
shadow (Ubuntu Focal): assignee |
|
Didier Roche (didrocks) |
|
| 2020-06-09 08:31:44 |
Didier Roche-Tolomelli |
shadow (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2020-06-09 08:31:45 |
Didier Roche-Tolomelli |
zsys (Ubuntu Focal): assignee |
|
Didier Roche (didrocks) |
|
| 2020-06-09 08:31:47 |
Didier Roche-Tolomelli |
zsys (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2020-06-09 08:31:50 |
Didier Roche-Tolomelli |
shadow (Ubuntu): status |
New |
Fix Released |
|
| 2020-06-09 09:04:00 |
Didier Roche-Tolomelli |
description |
Ideally, we would untag them as part of GC so that we can clean them up later. However, those can be linked to states on other pools with same pool name than targetted one, and it will be hard to match them.
Give a command for users to see them in status and then manually remove suspicious datasets ? |
[Impact]
* Deleting users were preserving corresponding ZFS user datasets, without marking them for cleanup.
* This is covered by dedicated use cases.
[Test Case]
1. Ensure you have a foo user:
2. Run userdel --remove foo
3. Check that rpool/USERDATA/foo_xxxx has its content removed and is not mounted
4. zfs get com.ubuntu.zsys:bootfs-dataset rpool/USERDATA/foo_xxxx is not associated with current system dataset
---
Other use case:
1.Ensure you have a foo user:
2. Run userdel foo
3. Check that rpool/USERDATA/foo_xxxx still has its content, but is not mounted.
4. zfs get com.ubuntu.zsys:bootfs-dataset rpool/USERDATA/foo_xxxx is not associated with current system dataset
---
On a non ZFS installation :
1. Ensure you have a foo user:
2. Run userdel --remove foo
3. The user is deleted, no error occured.
---
On a non ZFS installation with ZSys installed :
1. Ensure you have a foo user:
2. Run userdel --remove foo
3. The user is deleted, no error occured.
[Regression Potential]
* A new hidden command is added, triggered by userdel.
* Tests are covering this new command and GRPC request.
* The methodology is similar to useradd and usermod. The dependency between shadow and zsys is weak on purpose:
- the ZSys hidden command is available and is a no-op if not called
- if calling the command failed on userdel, nothing is done on ZSys side, but the code path is similar to ZSys not being installed or running on a non ZFS system.
----
Ideally, we would untag them as part of GC so that we can clean them up later. However, those can be linked to states on other pools with same pool name than targetted one, and it will be hard to match them.
Give a command for users to see them in status and then manually remove suspicious datasets ? |
|
| 2020-06-19 06:36:16 |
Timo Aaltonen |
zsys (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2020-06-19 06:36:17 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-06-19 06:36:20 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2020-06-19 06:36:22 |
Timo Aaltonen |
tags |
|
verification-needed verification-needed-focal |
|
| 2020-06-23 21:08:02 |
Brian Murray |
shadow (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2020-06-24 09:39:45 |
Jean-Baptiste Lallement |
tags |
verification-needed verification-needed-focal |
verification-done verification-done-focal |
|
| 2020-07-02 08:29:30 |
Launchpad Janitor |
shadow (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-07-02 08:29:32 |
Launchpad Janitor |
zsys (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-07-02 08:29:52 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
