Bug 1438675
| Summary: | Include gdeploy multipath disable script | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | SATHEESARAN <sasundar> |
| Component: | Documentation | Assignee: | Laura Bailey <lbailey> |
| Status: | CLOSED NOTABUG | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.2 | CC: | jbrooks, joherr, rhs-bugs, sabose, sankarshan, storage-doc, storage-qa-internal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-05-22 07:28:42 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1438596 | ||
| Bug Blocks: | |||
|
Description
SATHEESARAN
2017-04-04 07:44:31 UTC
@Sahina, Can we have this informatiom documented ? Is the step look correct ? (In reply to SATHEESARAN from comment #1) > @Sahina, > > Can we have this informatiom documented ? > Is the step look correct ? As long as the script is only blacklisting devices, and not disabling multipath - yes, it looks correct. Small update to the content: Blacklist all the local devices using the following gdeploy ansible module after [service2] [shell2] action=execute command=vdsm-tool configure --force # Disable multipath [script3] action=execute file=/usr/share/ansible/gdeploy/scripts/disable-multipath.sh In the above snip, I have changed [script2] to [script3] as there was already a section as [script2] in the generated gdeploy config file Please wait working on this documentation. Looks like Devyani is trying to fix it[1]. If it doesn't make it in to the release, then we need to document the same [1] - https://bugzilla.redhat.com/show_bug.cgi?id=1438596 Closing this bug, as the actual issue ( BZ - https://bugzilla.redhat.com/show_bug.cgi?id=1438596 ) is fixed with RHV 4.1.2 |