Description of problem: ----------------------- This installation issue is seen with independent mode of installation of OCS 3.10 in a brown field fashion OC cluster setup was up, post that trying to setup registry, logging & metrics. While doing that used the same playbook ( used to create OC cluster ) with parameters required for registry, logging & metrics. On the deployment ( playbooks/openshift-gluster/config.yml ), ansible tries to create heketi pod once again and fails as the bricks are already carved out of /dev/sdd. Version-Release number of selected component (if applicable): -------------------------------------------------------------- OCP 3.10 RHGS 3.4.0 nightly ( glusterfs-3.12.2-18.el7rhgs ) How reproducible: ----------------- consistent ( 6/6 ) Steps to Reproduce: -------------------- 1. Run the ansible playbook - playbooks/deploy_cluster.yml - to deploy cluster ( with the inventory file attached, referred as inventory1 ) 2. Add the registry, logging & parameters related parameters to the same inventory file ( inventory2 ) 3. Run the ansible playbook - playbooks/openshift-glusterfs/config.yml - to deploy registry, logging & metric related pods. Actual results: --------------- Deployment of registry, logging & metrics fails as the ansible once again tries to create heketi pod, which is already available Expected results: ----------------- Deployment of registry, logging & metrics should happen successfully Additional info:
Created attachment 1479753 [details] inventory file used to deploy oc cluster and heketi
Created attachment 1479754 [details] inventory file used to deploy registry,logging and metrics
Created attachment 1479755 [details] ansible log file corresponding to oc cluster deploy
Created attachment 1479756 [details] ansible log file corresponding to oc cluster deploy
Created attachment 1479758 [details] ansible log file corresponding to registry,logging and metrics
You cannot install OCS more than once. By having the [glusterfs] group in the second inventory file you are indicating to the playbook that these are new nodes to be installed. Closing this as NOTABUG.