Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-14450

test-operator images use RELATED_IMAGE interface... but we aren't releasing them downstream

XMLWordPrintable

    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • openstack-operator-bundle-container-1.0.7-9
    • None
    • Release Note Not Required
    • Critical

      The test-operator has 3 image which use the RELATED_IMAGE pattern/interface that don't exist downstream as in there are no product facing images for them. These env variables are named: RELATED_IMAGE_TEST_TOBIKO_IMAGE_URL_DEFAULT, RELATED_IMAGE_TEST_ANSIBLETEST_IMAGE_URL_DEFAULT, RELATED_IMAGE_TEST_HORIZONTEST_IMAGE_URL_DEFAULT.

      For FR1 the test-operator upstream used these env variables, and they also got used for internal test environments (UNI tests, etc). Downstream was removing them on the fly with this: https://gitlab.cee.redhat.com/osp-release/rhoso-release-scripts/-/blob/main/bundles/bundle-transmogrify.sh?ref_type=heads#L323

      For FR2 test-operator is now installed as part of openstack-operator, and these images are also managed as part of the OpenStackVersion interface. But there are no plans to ever deploy these images in a product facing manner... they are only used for internal testing. To avoid further build automation issues and confusion these images should drop use of the RELATED_IMAGE pattern and instead just be normal environment variables. This will avoid bundle build validations issues with them not existing (or getting ripped out), but also preserves the internal test interfaces required for these containers.

              dprince@redhat.com Dan Prince
              dprince@redhat.com Dan Prince
              rhos-dfg-ospk8s
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: