Bug 1563923
| Summary: | [Gdeploy+Ganesha] If pcs auth command fails while setting up ganesha cluster,gdeploy still proceed further with ganesha cluster creation | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Manisha Saini <msaini> |
| Component: | gdeploy | Assignee: | Devyani Kota <dkota> |
| Status: | CLOSED ERRATA | QA Contact: | Manisha Saini <msaini> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.3 | CC: | dkota, musoni, pmulay, rcyriac, rhinduja, rhs-bugs, smohan, storage-qa-internal |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.3.1 Async | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | gdeploy-2.0.2-26 | Doc Type: | If docs needed, set a value |
| Doc Text: |
Previously, despite failed PCS authentication, NFS Ganesha installation would proceed and execute further steps. A new flag ‘ignore_ganesha_errors’ is introduced with this update. Which can be set either 'yes' or 'no' to control the execution. If set to yes, errors will be ignored. If set to no, execution stops at the first error.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-06-21 03:33:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1581561 | ||
|
Description
Manisha Saini
2018-04-05 04:18:46 UTC
Commit #8145 [1] fixes this issue. [1]https://github.com/gluster/gdeploy/pull/501/commits/8556d566574bc676b2a6faffd067f7dc48d88145 Thanks. @pmulay, yes. looks good. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:1958 |