Story (Required)

As a pipelines service developer trying to deploy OSP nightly build in RHTAP, I'm facing an issue with one of the images being mirrored on a registry which (name) can't be resolved from outside of the company VPN.

 Status:
  Bundle Lookups:
    Catalog Source Ref:
      Name:       custom-operators
      Namespace:  openshift-marketplace
    Conditions:
      Message:               bundle contents have not yet been persisted to installplan status
      Reason:                BundleNotUnpacked
      Status:                True
      Type:                  BundleLookupNotPersisted
      Last Transition Time:  2023-10-03T10:17:39Z
      Message:               unpack job not completed: Unpack pod(openshift-marketplace/9bc5b721a7217fa945b0b203840b3b77641e5e50f6a857f030627b03beqnprc) container(pull) is pending. Reason: ImagePullBackOff, Message: Back-off pulling image "registry-proxy.engineering.redhat.com/rh-osbs/openshift-pipelines-pipelines-operator-bundle-container@sha256:34e559acf478af9ea868960ad24b12f281e0ca629f8de48b17b2a67814572a1e" 

and more specifically

pod/9bc5b721a7217fa945b0b203840b3b77641e5e50f6a857f030627b03beqnprc   Failed to pull image "registry-proxy.engineering.redhat.com/rh-osbs/openshift-pipelines-pipelines-operator-bundle-container@sha256:34e559acf478af9ea868960ad24b12f281e0ca629f8de48b17b2a67814572a1e": rpc error: code = Unknown desc = pinging container registry registry-proxy.engineering.redhat.com: Get "https://registry-proxy.engineering.redhat.com/v2/": dial tcp: lookup registry-proxy.engineering.redhat.com on 10.0.0.2:53: no such host 

Background (Required)

The issue is reproducible on ROSA HCP clusters as used by RHTAP and not a ROSA cluster provisioned by ClusterBot. The hostname part of the source URL registry-proxy.engineering.redhat.com is obviously only resolvable when not connected to the Red Hat VPN.

Notably only a single image (out of 883) is using that Registry hostname.

Out of scope

<Defines what is not included in this story>

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met