Bug 1502054
Summary: | glusterfs installation failed: parameter TOPOLOGY_PATH is required and must be specified | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Hongkai Liu <hongkliu> |
Component: | Installer | Assignee: | Jose A. Rivera <jarrpa> |
Status: | CLOSED ERRATA | QA Contact: | Hongkai Liu <hongkliu> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.7.0 | CC: | aos-bugs, hongkliu, jokerman, mifiedle, mmccomas |
Target Milestone: | --- | ||
Target Release: | 3.7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: |
undefined
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-11-28 22:17: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: |
Description
Hongkai Liu
2017-10-13 20:07:10 UTC
PR is upstream: https://github.com/openshift/openshift-ansible/pull/5667 Verified with: [fedora@ip-172-31-33-174 openshift-ansible]$ git log --oneline -1 b8879b5c6 (HEAD -> glusterfs) GlusterFS: remove topology reference from deploy-heketi root@ip-172-31-15-103: ~ # oc version oc v3.7.0-0.153.0 It passed the tasked of creating heketi pod in this bug, but got error later on TASK [openshift_storage_glusterfs : Create heketi DB volume]. I will attach the log later. PR for latest bug is upstream: https://github.com/openshift/openshift-ansible/pull/5769 Verified: Thanks for the quick fix. [fedora@ip-172-31-33-174 openshift-ansible]$ git log --oneline -2 3d3853836 (HEAD -> glusterfs2) GlusterFS: Remove image option from heketi command 27321df00 (origin/master, origin/HEAD, master) Merge pull request #5667 from jarrpa/deploy-heketi-fix-3.7 root@ip-172-31-11-69: ~ # oc version oc v3.7.0-0.153.0 [fedora@ip-172-31-33-174 ~]$ ansible-playbook -i /tmp/2.file openshift-ansible/playbooks/byo/openshift-glusterfs/config.yml PLAY RECAP ******************************************************************************************************************** ec2-54-186-162-10.us-west-2.compute.amazonaws.com : ok=47 changed=4 unreachable=0 failed=0 ec2-54-187-203-117.us-west-2.compute.amazonaws.com : ok=47 changed=4 unreachable=0 failed=0 ec2-54-200-62-253.us-west-2.compute.amazonaws.com : ok=47 changed=4 unreachable=0 failed=0 ec2-54-202-151-185.us-west-2.compute.amazonaws.com : ok=107 changed=38 unreachable=0 failed=0 ec2-54-213-59-28.us-west-2.compute.amazonaws.com : ok=44 changed=2 unreachable=0 failed=0 localhost : ok=12 changed=0 unreachable=0 failed=0 INSTALLER STATUS ************************************************************************************************************** Initialization : Complete etcd Install : Not Started NFS Install : Not Started Load balancer Install : Not Started Master Install : Not Started Master Additional Install : Not Started Node Install : Not Started GlusterFS Install : Complete Hosted Install : Not Started Metrics Install : Not Started Logging Install : Not Started Service Catalog Install : Not Started Management Install : Not Started Jose A. Rivera: another thought. I noticed that "GlusterFS Install" is before "Hosted Install" in the playbook summary (see Comment 7). Should it be the other way around like Metrics or Logging install? I did verification of the fix on an existing gluster. During the tests on a new gluster last Friday, glusterfs failed on very early stage. My guess would be that it depends on tasks in "Hosted Install". That was why I stepped back and started to install on an existing cluster. Let me know what you think about the ordering of the playbook. If I remember correctly, "Hosted Install" in this case is for the hosted registry. In this case, GlusterFS MUST come first if it is to provide storage for the hosted registry, and indeed for Logging and Metrics as well. I see. Thanks for the explanation. 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/RHSA-2017:3188 |