RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
It will be very convenient for users if we can provide a kind of rollback function like docker-storage-rollback when fail to create backend storage(VG, LVM, etc) for docker via docker-storage-setup, a similar idea is also to provide docker-storage-cleanup to support removing created storage by docker-storage-setup for users. 


Version-Release number of selected component (if applicable):
# rpm -q kernel docker
kernel-3.10.0-289.el7.x86_64
docker-1.7.1-115.el7.x86_64


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

While it will be convenient, I think it is not trivial at the same time this path will be filled with various kind of errors.

- First of all d-s-s will have to have some kind of persistent data which keeps
  track of all the actions d-s-s performed. So that these actions can be rolled
  back.

- If user created some volumes or directories which have same name what d-s-s uses then cleanup will remove those too and user will lose data.

So I prefer that we document it and let user do the cleanup manually, carefully making sure they are not losing any important data they might want to retain.

(In reply to Vivek Goyal from comment #2)
> - If user created some volumes or directories which have same name what
> d-s-s uses then cleanup will remove those too and user will lose data.
> 

Perhaps, the docker-migrate script can help save important data before removing storage.