Uploaded image for project: 'OpenShift Node'
  1. OpenShift Node
  2. OCPNODE-3330

fix origin test aws-ovn-ipv4 mcp status update delay

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • None
    • None
    • OCP Node Sprint 272 (Blue)

      https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-multiarch-master-nightly-4.20-ocp-e2e-aws-ovn-techpreview-serial-multi-a-a/1927866348751294464

      From the test log:https://prow.ci.openshift.org/4c05581b-a401-48fd-b962-4266f5279c29

        imagepolicy.config.openshift.io/public-key-rekor-image-policy created
  I0527 12:19:02.344384 11734 helpers.go:1307] Waiting for pool worker to complete rendered-worker-02d721064d289f66907b3806fc3cb13c
  I0527 12:21:22.466697 11734 helpers.go:1307] Waiting for pool master to complete rendered-master-e31d2639396b28bc115e23c22ab49b87
    STEP: launching the pod: signature-validation-test-pod @ 05/27/25 12:21:22.471

      waitforpoolcomplete function returns false positive result so the pod launced with the imagepolicy rollout finished.

      One of the resons of the falure is the mcp pool does not start updating immediately. I want to change the test to not use oc cli tool, use the client-go directly apply the CRD through go struct.

              qiwan233 Qi Wang
              qiwan233 Qi Wang
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: