Revert "OCPBUGS-19106: Updating ose-cluster-config-operator-container image to be consistent with ART"

[wking]

Reverts #385

It's complicated, but while ART is building RHEL 9 HyperShift and cluster-config-operator images, both ART and CI are building mostly-RHEL-8 machine-config operator images. HyperShift invokes both some machine-config-* and the cluster-config-operator binaries. And the MCO binaries are currently RHEL 8 both in CI and in ART builds. Moving the CI cluster-config operator back to RHEL 8 might give us some breathing room vs. current 4.15 release-controller blocker failures like:

=== NAME  TestCreateClusterProxy/ValidateHostedCluster
   util.go:218:
       failed to ensure guest nodes became ready, ready: (0/2):
       Unexpected error:
           <wait.errInterrupted>:
           timed out waiting for the condition

Because of NodePool failures like:

 - lastTransitionTime: "2023-12-04T17:38:58Z"
    message: |-
      Failed to generate payload: error getting ignition payload: failed to execute cluster-config-operator: cluster-config-operator process failed: /payloads/get-payload431072810/bin/cluster-config-operator: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /payloads/get-payload431072810/bin/cluster-config-operator)
      /payloads/get-payload431072810/bin/cluster-config-operator: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by /payloads/get-payload431072810/bin/cluster-config-operator)
      : exit status 1
    observedGeneration: 1
    reason: InvalidConfig
    status: ""
    type: ValidGeneratedPayload

[openshift-ci-robot]

@wking: This pull request references Jira Issue OCPBUGS-19106, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Reverts #385

It's complicated, but while ART is building RHEL 9 HyperShift and cluster-config-operator images, both ART and CI are building mostly-RHEL-8 machine-config operator images. HyperShift invokes both some machine-config-* and the cluster-config-operator binaries. And the MCO binaries are currently RHEL 8 both in CI and in ART builds. Moving the CI cluster-config operator back to RHEL 8 might give us some breathing room vs. current 4.15 release-controller blocker failures like:

=== NAME  TestCreateClusterProxy/ValidateHostedCluster
  util.go:218:
      failed to ensure guest nodes became ready, ready: (0/2):
      Unexpected error:
          <wait.errInterrupted>:
          timed out waiting for the condition

Because of NodePool failures like:

- lastTransitionTime: "2023-12-04T17:38:58Z"
   message: |-
     Failed to generate payload: error getting ignition payload: failed to execute cluster-config-operator: cluster-config-operator process failed: /payloads/get-payload431072810/bin/cluster-config-operator: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /payloads/get-payload431072810/bin/cluster-config-operator)
     /payloads/get-payload431072810/bin/cluster-config-operator: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by /payloads/get-payload431072810/bin/cluster-config-operator)
     : exit status 1
   observedGeneration: 1
   reason: InvalidConfig
   status: ""
   type: ValidGeneratedPayload

Instructions 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/test-infra repository.

[wking]

/payload-job periodic-ci-openshift-hypershift-release-4.15-periodics-e2e-aws-ovn

[openshift-ci]

@wking: trigger 1 job(s) for the /payload-(job|aggregate) command

• periodic-ci-openshift-hypershift-release-4.15-periodics-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/6c793360-93da-11ee-880c-32a0717f039d-0

[wking]

The previous payload attempt hasn't launched a run as far as I can tell. Trying again:

/payload-job periodic-ci-openshift-hypershift-release-4.15-periodics-e2e-aws-ovn

[openshift-ci]

@wking: trigger 1 job(s) for the /payload-(job|aggregate) command

• periodic-ci-openshift-hypershift-release-4.15-periodics-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/2785c6a0-93e0-11ee-8ddc-1689964b569c-0

[JoelSpeed]

Still didn't seem to work, let's try again
/payload-job periodic-ci-openshift-hypershift-release-4.15-periodics-e2e-aws-ovn

[openshift-ci]

@JoelSpeed: trigger 1 job(s) for the /payload-(job|aggregate) command

• periodic-ci-openshift-hypershift-release-4.15-periodics-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/a1e350f0-9414-11ee-89ff-2a13910a9c34-0

[JoelSpeed]

/lgtm

Based on https://redhat-internal.slack.com/archives/C068LS7RS6S/p1701834669669239 I don't think we need to run the HyperShift tests, not sure why the payload job isn't triggering correctly

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed, wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [JoelSpeed]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[JoelSpeed]

/override ci/prow/e2e-upgrade

Failures appear to be unrelated

[openshift-ci]

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-upgrade

In response to this:

/override ci/prow/e2e-upgrade

Failures appear to be unrelated

Instructions 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/test-infra repository.

[openshift-ci]

@wking: all tests passed!

Full PR test history. Your PR dashboard.

Instructions 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/test-infra repository. I understand the commands that are listed here.

[wking]

/jira refresh

[openshift-ci-robot]

@wking: This pull request references Jira Issue OCPBUGS-19106, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.0) matches configured target version for branch (4.15.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @gangwgr

In response to this:

/jira refresh

Instructions 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/test-infra repository.

[openshift-ci-robot]

@wking: Jira Issue OCPBUGS-19106: All pull requests linked via external trackers have merged:

• openshift/cluster-config-operator#353
• openshift/cluster-config-operator#385
• openshift/cluster-config-operator#388

Jira Issue OCPBUGS-19106 has been moved to the MODIFIED state.

In response to this:

Reverts #385

It's complicated, but while ART is building RHEL 9 HyperShift and cluster-config-operator images, both ART and CI are building mostly-RHEL-8 machine-config operator images. HyperShift invokes both some machine-config-* and the cluster-config-operator binaries. And the MCO binaries are currently RHEL 8 both in CI and in ART builds. Moving the CI cluster-config operator back to RHEL 8 might give us some breathing room vs. current 4.15 release-controller blocker failures like:

=== NAME  TestCreateClusterProxy/ValidateHostedCluster
  util.go:218:
      failed to ensure guest nodes became ready, ready: (0/2):
      Unexpected error:
          <wait.errInterrupted>:
          timed out waiting for the condition

Because of NodePool failures like:

- lastTransitionTime: "2023-12-04T17:38:58Z"
   message: |-
     Failed to generate payload: error getting ignition payload: failed to execute cluster-config-operator: cluster-config-operator process failed: /payloads/get-payload431072810/bin/cluster-config-operator: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /payloads/get-payload431072810/bin/cluster-config-operator)
     /payloads/get-payload431072810/bin/cluster-config-operator: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by /payloads/get-payload431072810/bin/cluster-config-operator)
     : exit status 1
   observedGeneration: 1
   reason: InvalidConfig
   status: ""
   type: ValidGeneratedPayload

Instructions 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/test-infra repository.

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-config-operator-container-v4.16.0-202312061430.p0.gc436b7a.assembly.stream for distgit ose-cluster-config-operator.
All builds following this will include this PR.