Uploaded image for project: 'OCP Technical Release Team'
  1. OCP Technical Release Team
  2. TRT-2106

AWS Techpreview Serial Timing Out Routinely, and broken in 4.20

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • None

      https://prow.ci.openshift.org/job-history/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview-serial

      Looks to have broken yesterday. In addition to the deprecated api issue, there are a few other tests popping up a lot.

      [sig-imagepolicy][OCPFeatureGate:SigstoreImageVerification][Serial] Should fail imagepolicy signature validation in different namespaces root of trust does not match the identity in the signature [Suite:openshift/conformance/serial]
      
      [sig-mco][OCPFeatureGate:MachineConfigNodes] [Serial]Should have MCN properties matching associated node properties for nodes in custom MCPs [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]
      
      [sig-mco][OCPFeatureGate:PinnedImages][OCPFeatureGate:MachineConfigNodes][Serial] Invalid PIS leads to degraded MCN in a custom Pool [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]
      
      [sig-mco][OCPFeatureGate:MachineConfigNodes] [Serial]Should properly transition through MCN conditions on rebootless node update [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]
      

      First started failing in https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview-serial/1920187644701052928 which ran 4.20.0-0.nightly-2025-05-07-183451

      https://issues.redhat.com/browse/OCPNODE-2999 would explain the SigstoreImageVerification tests.

      MCO tests I cannot explain, they do not fail every run, it seems to be just one at a time. Perhaps they slipped in with an earlier payload.

      The job also seems to routinely run over 5h hour, which also seemed to start at the same time.

              kenzhang@redhat.com Ken Zhang
              rhn-engineering-dgoodwin Devan Goodwin
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: