Bug 1740035
| Summary: | [IPI on Azure]Status.storage.azure.container doesn't be updated after specify a custom contianer | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | XiuJuan Wang <xiuwang> |
| Component: | Image Registry | Assignee: | Corey Daley <cdaley> |
| Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.2.0 | CC: | aos-bugs, cdaley |
| Target Milestone: | --- | ||
| Target Release: | 4.2.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: | 2019-10-16 06:35:36 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: | |||
I see what the issue is, the operator is not currently handling the case of a name being supplied, i'll put together a pull request Status.storage.azure.container has been updated after specify a custom container
$ oc describe config.image | grep Container -B4
Max Wait In Queue: 0s
Storage:
Azure:
Account Name: qexiuwangazure911j4xt92j
Container: qe-xiuwang-azure-911-j4rg2-test
Status:
Conditions:
Last Transition Time: 2019-09-11T01:25:20Z
Message: Storage container exists
Reason: ContainerExists
--
Ready Replicas: 0
Storage:
Azure:
Account Name: qexiuwangazure911j4xt92j
Container: qe-xiuwang-azure-911-j4rg2-test
Verified with payload 4.2.0-0.nightly-2019-09-10-235718
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/RHBA-2019:2922 |
Description of problem: Status.storage.azure.container doesn't be updated after specify a custom contianer Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-08-10-002649 How reproducible: always Steps to Reproduce: 1.Edit Spec.storage.azure.container to a custom one. $oc patch config.imageregistry cluster -p '{"spec":{"storage":{"azure":{"container":"testtestabcd"}}}}' --type=merge 2.Check container if takes effect. 3. Actual results: image registry pod has recreated with new storage container with seveval mins, but Status.storage.azure.container is still old one. $ oc set env deployment image-registry --list | grep AZURE REGISTRY_STORAGE_AZURE_CONTAINER=testtestabcd REGISTRY_STORAGE_AZURE_ACCOUNTNAME=qexiuwang812azurekvhxxj4 $ oc describe config.imageregistry | grep Container Container: testtestabcd Reason: ContainerExists Container: qe-xiuwang-812-azure-kvdgw-image-registry-f052ff2abcc211e98ca3 [wxj@dhcp-140-124 kubecon]$ oc describe config.imageregistry | grep Container -B4 Max Wait In Queue: 0s Storage: Azure: Account Name: qexiuwang812azurekvhxxj4 Container: testtestabcd -- Ready Replicas: 0 Storage: Azure: Account Name: qexiuwang812azurekvhxxj4 Container: qe-xiuwang-812-azure-kvdgw-image-registry-f052ff2abcc211e98ca3 Expected results: Should update Status.storage.azure.container as Spec.storage.azure.container Additional info: