Bug 1408695
Summary: | cns-deploy should NOT try to re-configure a working setup and end up aborting the deployment on executing it for the second time | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Prasanth <pprakash> |
Component: | cns-deploy-tool | Assignee: | Raghavendra Talur <rtalur> |
Status: | CLOSED ERRATA | QA Contact: | Prasanth <pprakash> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | cns-3.4 | CC: | dmesser, hchiramm, jarrpa, mliyazud, pprakash, rcyriac, vinug |
Target Milestone: | --- | ||
Target Release: | CNS 3.5 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | cns-deploy-4.0.0-2.el7rhgs | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-04-20 18:26:21 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: | 1415598 |
Description
Prasanth
2016-12-26 12:43:50 UTC
There is a flag called '--load' which starts the execution from topology load. Appreciated if you can validate this report wrt to the same. (In reply to Humble Chirammal from comment #1) > There is a flag called '--load' which starts the execution from topology > load. Appreciated if you can validate this report wrt to the same. That flag might not help here in this use case and I was not trying to resume from the topology load. Rather it was a fully configured setup on which the deletion of reources happened on a second run. So we should ideally prevent this from automatically happen patch posted at https://github.com/gluster/gluster-kubernetes/pull/175 (In reply to Raghavendra Talur from comment #7) > patch posted at https://github.com/gluster/gluster-kubernetes/pull/175 Merged. Verified ########## # cns-deploy -n storage-project -g -c oc -y -l /var/log/1-cns-deploy.log -v Using OpenShift CLI. NAME STATUS AGE storage-project Active 5d Using namespace "storage-project". Checking that heketi pod is not running ... Checking status of pods matching 'glusterfs=heketi-pod': heketi-1-lhqfh 1/1 Running 0 2d Found heketi pod running. Please destroy existing setup and try again. # cns-deploy -n storage-project -c oc -y -l /var/log/2-cns-deploy.log -v Using OpenShift CLI. NAME STATUS AGE storage-project Active 5d Using namespace "storage-project". Checking that heketi pod is not running ... Checking status of pods matching 'glusterfs=heketi-pod': heketi-1-lhqfh 1/1 Running 0 2d Found heketi pod running. Please destroy existing setup and try again. ########## *** Bug 1437792 has been marked as a duplicate of this bug. *** 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-2017:1112 Marking qe-test-coverage as - since the preferred mode of deployment is using ansible |