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

Bug 1482740

Summary: During install - the docker config file is mounted separately after install - due to selinux changes the update of parameters fail.
Product: OpenShift Container Platform Reporter: Glenn West <gwest>
Component: Image RegistryAssignee: Cesar Wong <cewong>
Status: CLOSED INSUFFICIENT_DATA QA Contact: ge liu <geliu>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: agladkov, aos-bugs, bparees, dyan, gwest
Target Milestone: ---   
Target Release: 3.8.0   
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: 2017-11-06 23:01:00 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 Glenn West 2017-08-18 03:00:53 UTC
Description of problem:

Using ocp 3.6 reference architecture auto deployment, the registry storage
does not get switched to azure blob. This is due to the failure to update
the .yml file that is updated during the config.

Duplication:

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

How reproducible:

Steps to Reproduce:
1. Deploy using: https://github.com/openshift/openshift-ansible-contrib/tree/master/reference-architecture/azure-ansible/ (Single VM Is fine)
2. Create nodejs test app
3. Observe if there is files in blob object.

Actual results:
No files - Checking registry its not using the right Azure Blob Storage.

Verified: Works fine in 3.5

Expected results:
Containers are stored on azure blob storage.

I believe this is related to:
https://bugzilla.redhat.com/show_bug.cgi?id=1481617

Note this is more related to "secrets" tha it is storage.

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:

Comment 2 Ben Parees 2017-10-05 04:01:21 UTC
Alexey bump.  Can we make the determination as to whether this was really the storage issue or something we need to look into further?

Comment 3 Ben Parees 2017-10-16 15:58:14 UTC
Cesar, as our resident azure expert, can you take a look into this?  Alexey can give you guidance as to what needs to be done to setup/recreate the issue.  Sounds like the current thinking is it's really a storage/mount issue, we just need to prove that.

Thanks

Comment 6 Cesar Wong 2017-10-30 20:08:37 UTC
Glenn, I am not able to successfully deploy using the azure-ansible repo at (https://github.com/openshift/openshift-ansible-contrib/tree/master/reference-architecture/azure-ansible). The script seems to think that I'm not using the usernamepassword method for RHEL registration and then fails. 

So a few questions:

1) Are you aware of the issue above and/or can you provision a single vm without any issues? If so, I'd like to understand what I'm doing wrong.

2) Do you have a deployed cluster where you are seeing this issue that I can take a look at?

2) Can you please clarify what you mean by "This is due to the failure to update
the .yml file that is updated during the config." Which yml file? and by config do you mean openshift-ansible install?