OCPBUGS-25045: Updating openshift-enterprise-tests-container image to be consistent with ART for 4.16

Updating openshift-enterprise-tests-container image to be consistent with ART for 4.16 TLDR: Product builds by ART can be configured for different base and builder images than corresponding CI builds. This automated PR requests a change to CI configuration to align with ART's configuration; please take steps to merge it quickly or contact ART to coordinate changes.

The configuration in the following ART component metadata is driving this alignment request: openshift-enterprise-tests.yml.

Detail:

This repository is out of sync with the downstream product builds for this component. The CI configuration for at least one image differs from ART's expected product configuration. This should be addressed to ensure that the component's CI testing accurate reflects what customers will experience.

Most of these PRs are opened as an ART-driven proposal to migrate base image or builder(s) to a different version, usually prior to GA. The intent is to effect changes in both configurations simultaneously without breaking either CI or ART builds, so usually ART builds are configured to consider CI as canonical and attempt to match CI config until the PR merges to align both. ART may also configure changes in GA releases with CI remaining canonical for a brief grace period to enable CI to succeed and the alignment PR to merge. In either case, ART configuration will be made canonical at some point (typically at branch-cut before GA or release dev-cut after GA), so it is important to align CI configuration as soon as possible.

PRs are also triggered when CI configuration changes without ART coordination, for instance to change the number of builder images or to use a different golang version. These changes should be coordinated with ART; whether ART configuration is canonical or not, preferably it would be updated first to enable the changes to occur simultaneously in both CI and ART at the same time. This also gives ART a chance to validate the intended changes first. For instance, ART compiles most components with the Golang version being used by the control plane for a given OpenShift release. Exceptions to this convention (i.e. you believe your component must be compiled with a Golang version independent from the control plane) must be granted by the OpenShift staff engineers and communicated to the ART team.

Roles & Responsibilities:

Component owners are responsible for ensuring these alignment PRs merge with passing tests OR that necessary metadata changes are reported to the ART team: @release-artists in #forum-ocp-art on Slack. If necessary, the changes required by this pull request can be introduced with a separate PR opened by the component team. Once the repository is aligned, this PR will be closed automatically.
Patch-manager or those with sufficient privileges within this repository may add any required labels to ensure the PR merges once tests are passing. In cases where ART config is canonical, downstream builds are already being built with these changes, and merging this PR only improves the fidelity of our CI. In cases where ART config is not canonical, this provides a grace period for the component team to align their CI with ART's configuration before it becomes canonical in product builds.

ART has been configured to reconcile your CI build root image (see https://docs.ci.openshift.org/docs/architecture/ci-operator/#build-root-image). In order for your upstream .ci-operator.yaml configuration to be honored, you must set the following in your openshift/release ci-operator configuration file:

build_root:
  from_repository: true

Change behavior of future PRs:

In case you just want to follow the base images that ART suggests, you can configure additional labels to be set up automatically. This means that such a PR would merge without human intervention (and awareness!) in the future. To do so, open a PR to set the auto_label attribute in the image configuration. Example
You can set a commit prefix, like UPSTREAM: <carry>:. An example.

If you have any questions about this pull request, please reach out to @release-artists in the #forum-ocp-art coreos slack channel.

Depends on PullRequest(title="OCPBUGS-30362: Updating ose-tools-container image to be consistent with ART for 4.16", number=1702) . Allow it to merge and then run /test all on this PR.

@openshift-bot: This pull request references Jira Issue OCPBUGS-25045, which is invalid:

expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED 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](https://github.com/openshift/origin/pull/28696): >Updating openshift-enterprise-tests-container image to be consistent with ART for 4.16 >__TLDR__: >Product builds by ART can be configured for different base and builder images than corresponding CI >builds. This automated PR requests a change to CI configuration to align with ART's configuration; >please take steps to merge it quickly or contact ART to coordinate changes. > >The configuration in the following ART component metadata is driving this alignment request: >[openshift-enterprise-tests.yml](https://github.com/openshift/ocp-build-data/tree/84085f757454321f0b6d7d2408189b399749c3ec/images/openshift-enterprise-tests.yml). > >__Detail__: > >This repository is out of sync with the downstream product builds for this component. The CI >configuration for at least one image differs from ART's expected product configuration. This should >be addressed to ensure that the component's CI testing accurate reflects what customers will >experience. > >Most of these PRs are opened as an ART-driven proposal to migrate base image or builder(s) to a >different version, usually prior to GA. The intent is to effect changes in both configurations >simultaneously without breaking either CI or ART builds, so usually ART builds are configured to >consider CI as canonical and attempt to match CI config until the PR merges to align both. ART may >also configure changes in GA releases with CI remaining canonical for a brief grace period to enable >CI to succeed and the alignment PR to merge. In either case, ART configuration will be made >canonical at some point (typically at branch-cut before GA or release dev-cut after GA), so it is >important to align CI configuration as soon as possible. > >PRs are also triggered when CI configuration changes without ART coordination, for instance to >change the number of builder images or to use a different golang version. These changes should be >coordinated with ART; whether ART configuration is canonical or not, preferably it would be updated >first to enable the changes to occur simultaneously in both CI and ART at the same time. This also >gives ART a chance to validate the intended changes first. For instance, ART compiles most >components with the Golang version being used by the control plane for a given OpenShift release. >Exceptions to this convention (i.e. you believe your component must be compiled with a Golang >version independent from the control plane) must be granted by the OpenShift staff engineers and >communicated to the ART team. > >__Roles & Responsibilities__: >- Component owners are responsible for ensuring these alignment PRs merge with passing > tests OR that necessary metadata changes are reported to the ART team: `@release-artists` > in `#forum-ocp-art` on Slack. If necessary, the changes required by this pull request can be > introduced with a separate PR opened by the component team. Once the repository is aligned, > this PR will be closed automatically. >- Patch-manager or those with sufficient privileges within this repository may add > any required labels to ensure the PR merges once tests are passing. In cases where ART config is > canonical, downstream builds are *already* being built with these changes, and merging this PR > only improves the fidelity of our CI. In cases where ART config is not canonical, this provides > a grace period for the component team to align their CI with ART's configuration before it becomes > canonical in product builds. > >ART has been configured to reconcile your CI build root image (see https://docs.ci.openshift.org/docs/architecture/ci-operator/#build-root-image). >In order for your upstream .ci-operator.yaml configuration to be honored, you must set the following in your openshift/release ci-operator configuration file: >``` >build_root: > from_repository: true >``` > >__Change behavior of future PRs__: >* In case you just want to follow the base images that ART suggests, you can configure additional labels to be > set up automatically. This means that such a PR would *merge without human intervention* (and awareness!) in the future. > To do so, open a PR to set the `auto_label` attribute in the image configuration. [Example](https://github.com/openshift-eng/ocp-build-data/pull/1778) >* You can set a commit prefix, like `UPSTREAM: : `. [An example](https://github.com/openshift-eng/ocp-build-data/blob/6831b59dddc5b63282076d3abe04593ad1945148/images/ose-cluster-api.yml#L11). > >If you have any questions about this pull request, please reach out to `@release-artists` in the `#forum-ocp-art` coreos slack channel. > >Depends on PullRequest(title="OCPBUGS-30362: Updating ose-tools-container image to be consistent with ART for 4.16", number=1702) . Allow it to merge and then run `/test all` on this PR. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-bot Once this PR has been reviewed and has the lgtm label, please assign stbenjam for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/openshift/origin/blob/master/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

@openshift-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-agnostic-ovn-cmd	0173ccc6289a74e8396c4107e8333472fe6eac43	link	false	`/test e2e-agnostic-ovn-cmd`
ci/prow/e2e-aws-ovn-single-node	0173ccc6289a74e8396c4107e8333472fe6eac43	link	false	`/test e2e-aws-ovn-single-node`
ci/prow/e2e-aws-csi	0173ccc6289a74e8396c4107e8333472fe6eac43	link	false	`/test e2e-aws-csi`
ci/prow/e2e-gcp-ovn	0173ccc6289a74e8396c4107e8333472fe6eac43	link	true	`/test e2e-gcp-ovn`
ci/prow/e2e-aws-ovn-upgrade	0173ccc6289a74e8396c4107e8333472fe6eac43	link	false	`/test e2e-aws-ovn-upgrade`
ci/prow/e2e-gcp-ovn-rt-upgrade	0173ccc6289a74e8396c4107e8333472fe6eac43	link	false	`/test e2e-gcp-ovn-rt-upgrade`
ci/prow/e2e-aws-ovn-cgroupsv2	0173ccc6289a74e8396c4107e8333472fe6eac43	link	false	`/test e2e-aws-ovn-cgroupsv2`
ci/prow/e2e-gcp-csi	0173ccc6289a74e8396c4107e8333472fe6eac43	link	false	`/test e2e-gcp-csi`
ci/prow/images	0173ccc6289a74e8396c4107e8333472fe6eac43	link	true	`/test images`
ci/prow/e2e-aws-ovn-single-node-upgrade	0173ccc6289a74e8396c4107e8333472fe6eac43	link	false	`/test e2e-aws-ovn-single-node-upgrade`
ci/prow/e2e-aws-ovn-fips	0173ccc6289a74e8396c4107e8333472fe6eac43	link	true	`/test e2e-aws-ovn-fips`
ci/prow/e2e-gcp-ovn-upgrade	0173ccc6289a74e8396c4107e8333472fe6eac43	link	true	`/test e2e-gcp-ovn-upgrade`
ci/prow/unit	0173ccc6289a74e8396c4107e8333472fe6eac43	link	true	`/test unit`
ci/prow/verify-deps	0173ccc6289a74e8396c4107e8333472fe6eac43	link	true	`/test verify-deps`
ci/prow/e2e-aws-ovn-serial	0173ccc6289a74e8396c4107e8333472fe6eac43	link	true	`/test e2e-aws-ovn-serial`
ci/prow/e2e-openstack-ovn	0173ccc6289a74e8396c4107e8333472fe6eac43	link	false	`/test e2e-openstack-ovn`
ci/prow/e2e-metal-ipi-ovn-ipv6	0173ccc6289a74e8396c4107e8333472fe6eac43	link	true	`/test e2e-metal-ipi-ovn-ipv6`
ci/prow/e2e-metal-ipi-sdn	0173ccc6289a74e8396c4107e8333472fe6eac43	link	false	`/test e2e-metal-ipi-sdn`
ci/prow/e2e-aws-ovn-single-node-serial	0173ccc6289a74e8396c4107e8333472fe6eac43	link	false	`/test e2e-aws-ovn-single-node-serial`
ci/prow/verify	0173ccc6289a74e8396c4107e8333472fe6eac43	link	true	`/test verify`

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

@openshift-bot: This pull request references Jira Issue OCPBUGS-25045. The bug has been updated to no longer refer to the pull request using the external bug tracker.

In response to [this](https://github.com/openshift/origin/pull/28696): >Updating openshift-enterprise-tests-container image to be consistent with ART for 4.16 >__TLDR__: >Product builds by ART can be configured for different base and builder images than corresponding CI >builds. This automated PR requests a change to CI configuration to align with ART's configuration; >please take steps to merge it quickly or contact ART to coordinate changes. > >The configuration in the following ART component metadata is driving this alignment request: >[openshift-enterprise-tests.yml](https://github.com/openshift/ocp-build-data/tree/3610d0c7370c5dc6c1c7051afea6c00d7304ee95/images/openshift-enterprise-tests.yml). > >__Detail__: > >This repository is out of sync with the downstream product builds for this component. The CI >configuration for at least one image differs from ART's expected product configuration. This should >be addressed to ensure that the component's CI testing accurate reflects what customers will >experience. > >Most of these PRs are opened as an ART-driven proposal to migrate base image or builder(s) to a >different version, usually prior to GA. The intent is to effect changes in both configurations >simultaneously without breaking either CI or ART builds, so usually ART builds are configured to >consider CI as canonical and attempt to match CI config until the PR merges to align both. ART may >also configure changes in GA releases with CI remaining canonical for a brief grace period to enable >CI to succeed and the alignment PR to merge. In either case, ART configuration will be made >canonical at some point (typically at branch-cut before GA or release dev-cut after GA), so it is >important to align CI configuration as soon as possible. > >PRs are also triggered when CI configuration changes without ART coordination, for instance to >change the number of builder images or to use a different golang version. These changes should be >coordinated with ART; whether ART configuration is canonical or not, preferably it would be updated >first to enable the changes to occur simultaneously in both CI and ART at the same time. This also >gives ART a chance to validate the intended changes first. For instance, ART compiles most >components with the Golang version being used by the control plane for a given OpenShift release. >Exceptions to this convention (i.e. you believe your component must be compiled with a Golang >version independent from the control plane) must be granted by the OpenShift staff engineers and >communicated to the ART team. > >__Roles & Responsibilities__: >- Component owners are responsible for ensuring these alignment PRs merge with passing > tests OR that necessary metadata changes are reported to the ART team: `@release-artists` > in `#forum-ocp-art` on Slack. If necessary, the changes required by this pull request can be > introduced with a separate PR opened by the component team. Once the repository is aligned, > this PR will be closed automatically. >- Patch-manager or those with sufficient privileges within this repository may add > any required labels to ensure the PR merges once tests are passing. In cases where ART config is > canonical, downstream builds are *already* being built with these changes, and merging this PR > only improves the fidelity of our CI. In cases where ART config is not canonical, this provides > a grace period for the component team to align their CI with ART's configuration before it becomes > canonical in product builds. > >ART has been configured to reconcile your CI build root image (see https://docs.ci.openshift.org/docs/architecture/ci-operator/#build-root-image). >In order for your upstream .ci-operator.yaml configuration to be honored, you must set the following in your openshift/release ci-operator configuration file: >``` >build_root: > from_repository: true >``` > >__Change behavior of future PRs__: >* In case you just want to follow the base images that ART suggests, you can configure additional labels to be > set up automatically. This means that such a PR would *merge without human intervention* (and awareness!) in the future. > To do so, open a PR to set the `auto_label` attribute in the image configuration. [Example](https://github.com/openshift-eng/ocp-build-data/pull/1778) >* You can set a commit prefix, like `UPSTREAM: : `. [An example](https://github.com/openshift-eng/ocp-build-data/blob/6831b59dddc5b63282076d3abe04593ad1945148/images/ose-cluster-api.yml#L11). > >If you have any questions about this pull request, please reach out to `@release-artists` in the `#forum-ocp-art` coreos slack channel. > >Depends on PullRequest(title="OCPBUGS-30362: Updating ose-tools-container image to be consistent with ART for 4.16", number=1702) . Allow it to merge and then run `/test all` on this PR. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

openshift / origin

OCPBUGS-25045: Updating openshift-enterprise-tests-container image to be consistent with ART for 4.16 #28696