Bug 1832083 - [DOC] document manual cleanup of brick volumes after failed deployment
Summary: [DOC] document manual cleanup of brick volumes after failed deployment
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Deploying_RHHI
Version: rhhiv-1.7
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
: RHHI-V 1.8
Assignee: Laura Bailey
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1825836
Blocks: RHHI-V-1.8-Documentation-Inflight-BZs
TreeView+ depends on / blocked
 
Reported: 2020-05-06 04:46 UTC by SATHEESARAN
Modified: 2020-08-11 13:15 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1825836
Environment:
Last Closed: 2020-08-11 13:15:16 UTC
Embargoed:


Attachments (Terms of Use)

Description SATHEESARAN 2020-05-06 04:46:20 UTC
Description of problem:
After a failed deployment of gluster-storage, the documentation is lacking the advises on manual cleanup of included bricks. This is leading to failures on a re-tried deployment

Version-Release number of selected component (if applicable):
https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infrastructure_for_virtualization/1.7/html/deploying_red_hat_hyperconverged_infrastructure_for_virtualization/tshoot-deploy-error#failed_to_deploy_storage

How reproducible:
Always

Steps to Reproduce:
1. Deploy storage (and fail for some reason)
2. Follow chapter 13 to clean up
3. Re-run deployment

Actual results:
Second deployment is failing due to existing VDO signatures on brick devices. These need to be manually cleaned up.

Expected results:
Documentation provides information on the need to do so.

Comment 1 SATHEESARAN 2020-05-06 04:47:40 UTC
I have specifically cloned this bug as the original bug reported by the customer is targeted for RHHI-V 1.7.z
and this bug is targeted for RHHI-V 1.8

Original bugs is https://bugzilla.redhat.com/show_bug.cgi?id=1825836

Comment 3 SATHEESARAN 2020-07-30 01:31:57 UTC
Verified with the doc link.

VDO cleanup steps are available as part of manual cleanup post failed deployment


Note You need to log in before you can comment on or make changes to this bug.