Bug 1272032
Summary: | Cluster is created even when devices are unavailable | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Anush Shetty <ashetty> |
Component: | heketi | Assignee: | Luis Pabón <lpabon> |
Status: | CLOSED ERRATA | QA Contact: | Bala Konda Reddy M <bmekala> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | unspecified | CC: | ashetty, asrivast, madam, mliyazud, nerawat, pprakash, rcyriac, sankarshan |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | RHGS Container Converged 1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | heketi-1.4.0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-08-04 04:49:40 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: | 1332128 |
Description
Anush Shetty
2015-10-15 10:21:11 UTC
Hi Anush, the issue found here is highlighted in the release notes https://github.com/heketi/heketi/releases/tag/1.0.0 as a Known Issue #133. We can keep this bug open to link it to https://github.com/heketi/heketi/issues/133, but it should not affect the release. - Luis Anush is there a way to 'defer' this bug since it does not apply to Release 1 of Heketi? (In reply to Luis Pabón from comment #3) > Anush is there a way to 'defer' this bug since it does not apply to Release > 1 of Heketi? (In reply to Luis Pabón from comment #4) > (In reply to Luis Pabón from comment #3) > > Anush is there a way to 'defer' this bug since it does not apply to Release > > 1 of Heketi? This doesn't have the acks here. So it could remain as is for now? Solved in 1.4.0. Please move to ON_QA This is a good catch, but this cannot be solved for this release. The fix would be too complicated. It has been fixed by BZ 1350625, so I guess it wasn't too hard 1.Loaded the topology and the cluster is created successfully for the first time. 2. loaded the topology file again with same hostname and details, No new cluster is created Expected: No new cluster is created sh-4.2# export HEKETI_CLI_SERVER=http://heketi-aplo.cloudapps.myaplo.com sh-4.2# vi topology.json sh-4.2# sh-4.2# heketi-cli topology load --json=topology.json Found node dhcp37-71.lab.eng.blr.redhat.com on cluster 2c553c93babc56ef0f6de385dcabb820 Found device /dev/vdc Found node dhcp37-72.lab.eng.blr.redhat.com on cluster 2c553c93babc56ef0f6de385dcabb820 Found device /dev/vdc Found node dhcp37-191.lab.eng.blr.redhat.com on cluster 2c553c93babc56ef0f6de385dcabb820 Found device /dev/vdc sh-4.2# sh-4.2# heketi-cli cluster list Clusters: 2c553c93babc56ef0f6de385dcabb820 Hence marking it as verified 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://rhn.redhat.com/errata/RHBA-2016-1498.html |