fix: add ipi-install-vsphere-registry to vsphere OVN WINC provision chain#76362
fix: add ipi-install-vsphere-registry to vsphere OVN WINC provision chain#76362weinliu wants to merge 1 commit intoopenshift:mainfrom
Conversation
…hain The cucushift-installer-rehearse-vsphere-ipi-ovn-winc-provision chain was missing the ipi-install-vsphere-registry step after ipi-install, causing the image registry to remain in Removed/Managed state without a backing store configured. This resulted in dockercfg secrets not being created in new namespaces, blocking Windows container e2e tests. Other vSphere provision chains (disconnected, proxy variants) already include this step correctly. This change aligns the OVN WINC chain with the established pattern.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: weinliu The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
@weinliu: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
2 participants
Summary
The
cucushift-installer-rehearse-vsphere-ipi-ovn-winc-provisionchain was missing theipi-install-vsphere-registrystep afteripi-install, causing the image registry to remain without a backing store configured. This resulted in dockercfg secrets not being created in new namespaces, blocking Windows container e2e tests.Other vSphere provision chains (disconnected, proxy variants) already include this step correctly. This change aligns the OVN WINC chain with the established pattern.
Root cause
ipi-install(generic chain) does not configure vSphere image registry storageipi-install-vsphere-registryis the vSphere-specific step that patches the registry with an NFS backing storeTest
Rehearsed with
pull-ci-openshift-openshift-tests-private-release-4.21-debug-winc-vsphere-ipi: theipi-install-vsphere-registrystep succeeded and subsequent Windows e2e tests ran as expected.