Bug 1433260
Summary: | cns_deploy command failed: The DeploymentConfig "heketi" is invalid | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Apeksha <akhakhar> |
Component: | cns-deploy-tool | Assignee: | Mohamed Ashiq <mliyazud> |
Status: | CLOSED ERRATA | QA Contact: | Apeksha <akhakhar> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | cns-3.5 | CC: | hchiramm, jarrpa, mliyazud, pprakash, rcyriac, vinug |
Target Milestone: | --- | Keywords: | TestBlocker |
Target Release: | CNS 3.5 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | cns-deploy-4.0.0-4.el7rhgs | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-04-20 18:27:48 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: | 1433304 | ||
Bug Blocks: | 1415600 |
Description
Apeksha
2017-03-17 08:45:04 UTC
Label cleanup [https://github.com/gluster/gluster-kubernetes/pull/154] needed few more stuff so these https://github.com/gluster/gluster-kubernetes/pull/191 and https://github.com/gluster/gluster-kubernetes/pull/199 were required. We skipped as we did not have a downstream BZ. Please add these two and do a Build. I verified it. It is working. Heketi is up and running after running cns_deploy on build: cns-deploy-4.0.0-9.el7rhgs.x86_64 heketi-client-4.0.0-4.el7rhgs.x86_64, 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://access.redhat.com/errata/RHEA-2017:1112 Marking qe-test-coverage as - since the preferred mode of deployment is using ansible |