Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1597484

Summary: on a greenfield OCP + CNS deployment, pods in default project is not configured
Product: OpenShift Container Platform Reporter: krishnaram Karthick <kramdoss>
Component: InstallerAssignee: Russell Teague <rteague>
Installer sub component: openshift-ansible QA Contact: Johnny Liu <jialiu>
Status: CLOSED WONTFIX Docs Contact:
Severity: unspecified    
Priority: unspecified CC: anli, aos-bugs, jarrpa, jokerman, kramdoss, mmccomas, xtian
Version: 3.10.0Keywords: Unconfirmed
Target Milestone: ---   
Target Release: 3.10.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-15 18:52:46 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:
Attachments:
Description Flags
hosts inventory file none

Description krishnaram Karthick 2018-07-03 03:44:25 UTC 
Description of problem:
When OCP + CNS is configured via ansible as a greenfield deployment, pods in default project is not configured. ie., router, registry console & docker registry.

However with the same inventory file, when deploy_cluster is run commenting out glusterfs section, these pods are configured properly.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. run deploy_cluster playbook with glusterfs section defined
2. check if pods in default project is deployed
3.

Actual results:
with ocp_cns greenfield deployment, pods in default project is not spun up

Expected results:
with ocp_cns greenfield deployment, pods in default project should be configured

Additional info:
Comment 1 krishnaram Karthick 2018-07-03 03:47:42 UTC 
Missed out to add the version details,

Version-Release number of selected component (if applicable):
openshift v3.10.10
kubernetes v1.10.0+b81c8f8
Comment 2 krishnaram Karthick 2018-07-03 03:51:12 UTC 
Created attachment 1456094 [details]
hosts inventory file
Comment 4 Scott Dodson 2018-07-03 12:12:29 UTC 
Do the pods not exist or are they failing for some reason? If they're failing can you debug why they're failing?
Comment 8 Scott Dodson 2019-11-15 18:52:46 UTC 
Closing this bug due to OpenShift versions < 3.11 exiting the full support phase. If this bug is still impacting releases >= 3.11 and your use cases, please reopen with those additional details and update the target release where you are impacted on a fully supported version of OpenShift.
Comment 9 Red Hat Bugzilla 2023-09-14 04:30:51 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days