[release-4.14] OCPBUGS-44002: Continuous pull-secret updates / slow initialization on build01 (test platform infrastructure)

[sanchezl]

Manual cherry-pick of https://github.com/openshift/cluster-image-registry-operator/pull/1136

[sanchezl]

/jira cherry-pick OCPBUGS-42930

[openshift-ci-robot]

@sanchezl: Detected clone of Jira Issue OCPBUGS-42930 with correct target version. Will retitle the PR to link to the clone. /retitle OCPBUGS-44002: compact duplicate external hostnames

In response to [this](https://github.com/openshift/cluster-image-registry-operator/pull/1152#issuecomment-2447400214): >/jira cherry-pick OCPBUGS-42930 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-image-registry-operator). 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-ci-robot]

@sanchezl: This pull request references Jira Issue OCPBUGS-44002, which is invalid:

• expected dependent Jira Issue OCPBUGS-42930 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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/cluster-image-registry-operator/pull/1152): > Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-image-registry-operator). 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-ci-robot]

@sanchezl: An error was encountered searching for dependent bug OCPBUGS-42930 for bug OCPBUGS-44002 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message.

No response returned: Get "https://issues.redhat.com/rest/api/2/issue/OCPBUGS-42930": GET https://issues.redhat.com/rest/api/2/issue/OCPBUGS-42930 giving up after 5 attempt(s)

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

In response to [this](https://github.com/openshift/cluster-image-registry-operator/pull/1152): >Manual cherry-pick of https://github.com/openshift/cluster-image-registry-operator/pull/1136 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-image-registry-operator). 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.

[flavianmissi]

/lgtm /label backport-risk-assessed

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: flavianmissi, sanchezl

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](https://github.com/openshift/cluster-image-registry-operator/blob/release-4.14/OWNERS)~~ [flavianmissi] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[wewang58]

/label cherry-pick-approved

[wewang58]

/test e2e-aws-ovn-upgrade

[wewang58]

/jira refresh

[openshift-ci-robot]

@wewang58: This pull request references Jira Issue OCPBUGS-44002, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target version (4.14.z) matches configured target version for branch (4.14.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * release note type set to "Release Note Not Required" * dependent bug [Jira Issue OCPBUGS-42930](https://issues.redhat.com//browse/OCPBUGS-42930) is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA)) * dependent [Jira Issue OCPBUGS-42930](https://issues.redhat.com//browse/OCPBUGS-42930) targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z * bug has dependents

Requesting review from QA contact: /cc @wewang58

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

In response to [this](https://github.com/openshift/cluster-image-registry-operator/pull/1152#issuecomment-2448933164): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-image-registry-operator). 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.

[xiuwang]

/retest

[openshift-ci[bot]]

@sanchezl: all tests passed!

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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[openshift-ci-robot]

@sanchezl: Jira Issue OCPBUGS-44002: All pull requests linked via external trackers have merged:

• openshift/cluster-image-registry-operator#1152

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

In response to [this](https://github.com/openshift/cluster-image-registry-operator/pull/1152): >Manual cherry-pick of https://github.com/openshift/cluster-image-registry-operator/pull/1136 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-image-registry-operator). 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-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-cluster-image-registry-operator This PR has been included in build ose-cluster-image-registry-operator-container-v4.14.0-202410310707.p0.ge41516d.assembly.stream.el8. All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.14.0-0.nightly-2024-10-31-123546