Bug 1949313 - Rename vmware-vsphere-* images to vsphere-* images before 4.8 ships
Summary: Rename vmware-vsphere-* images to vsphere-* images before 4.8 ships
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.8.0
Assignee: Fabio Bertinatto
QA Contact: Wei Duan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-14 00:25 UTC by Clayton Coleman
Modified: 2021-07-27 23:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-27 23:00:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 23:00:38 UTC

Description Clayton Coleman 2021-04-14 00:25:32 UTC 
The images vmware-vsphere-csi-driver-operator and vmware-vsphere-csi-driver must be renamed to vsphere-csi-driver and vsphere-csi-driver-operator before we ship 4.8, since we don't include vendor names in our drivers and the label would give the implication these drivers are supported by vmware (we don't call the gcp driver google-gcp).

May not be deferred from 4.8
Comment 1 Fabio Bertinatto 2021-04-14 10:59:07 UTC 
This is what we've done so far:

Rename CI images: https://github.com/openshift/release/pull/17472
Rename ART images: https://github.com/openshift/ocp-build-data/pull/879
Update image-references: https://github.com/openshift/cluster-storage-operator/pull/149 and https://github.com/openshift/cluster-storage-operator/pull/155
Comet request (driver): https://projects.engineering.redhat.com/browse/CLOUDDST-5731
Comet request (operator): https://projects.engineering.redhat.com/browse/CLOUDDST-5736

The latest CI release (4.8.0-0.ci-2021-04-14-103744) has the renamed images already. The latest nightly (4.8.0-0.nightly-2021-04-13-171608) does not.

We'll follow up once a new nightly build is available.
Comment 2 Jan Safranek 2021-04-16 14:36:53 UTC 
Is there anything remaining to be fixed?
Comment 3 Fabio Bertinatto 2021-04-19 08:05:09 UTC 
This is complete now. Both CI and ART images contained the renamed images.

For the record, in order to renamed the images, I've followed the steps described here: https://docs.ci.openshift.org/docs/how-tos/onboarding-a-new-component/#removing-or-renaming-an-image-from-an-openshift-release-image
Comment 6 Wei Duan 2021-04-20 03:35:47 UTC 
Verified pass. 

$ oc adm release info  --pullspecs=true | grep vsphere
  vsphere-csi-driver                             quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:323bf3d1622beba621ab99966859c3688f3385bde7cfb2a93c8b9f2515033961
  vsphere-csi-driver-operator                    quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:fc80656db8631d5752111e4aaaae9eb05d3ab8e5d74f3327a6688d36c91bfa23
  vsphere-csi-driver-syncer                      quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ad36f363f01dc1dbcae21640e6ccba749e7f830a6562410121d0266bc87be782
  vsphere-problem-detector                       quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:c6de3f30f03182ba5ee60d3714c88d2fca8a0c18c605fe56e3ca81d0bc4ae6b2

And checked in brew:
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1579068
registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-vsphere-csi-driver:v4.8.0-202104162013.p0
Comment 9 errata-xmlrpc 2021-07-27 23:00:23 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:2438
Note You need to log in before you can comment on or make changes to this bug.