Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 482085[details]
vdsm.log
* Domain creation failed for "MkfsError: Cannot create filesystem on device".
* Devices were left dirty, even though they are not used.
* Devices should be cleaned, so they could be re-used for future domains.
(In reply to comment #5)
> (In reply to comment #4)
> > How do I reproduce this bug?
>
> It happens every time when using the storage at Westford: http://10.16.45.61
Can you specify which actions produced this error?
While some errors are susceptible to rollback, reliably rollbacking from any error that might arise in blockSD.create is unfortunately impossible. Hence, I claim it's a futile task in the first place.
There is, however, a mechanism for handling errors exactly such as this: VDSM uses the domain tags to communicate whether the domain is ready or not (RHAT_storage_domain_UNREADY). While that tag is set the VG should not be used, and should be considered as marked for deletion.
This tagging mechanism seems to work reliably for failures in mkfs, therefor this doesn't appear to be a bug.
Created attachment 482085 [details] vdsm.log * Domain creation failed for "MkfsError: Cannot create filesystem on device". * Devices were left dirty, even though they are not used. * Devices should be cleaned, so they could be re-used for future domains.