Bug 2031938 - CI tests needed to confirm driver-toolkit image contents
Summary: CI tests needed to confirm driver-toolkit image contents
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Driver Toolkit
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.z
Assignee: dagray
QA Contact: Walid A.
Depends On: 2031854
TreeView+ depends on / blocked
Reported: 2021-12-13 18:29 UTC by OpenShift BugZilla Robot
Modified: 2022-01-05 16:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-01-05 16:12:09 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift driver-toolkit pull 72 0 None open [release-4.8] Bug 2031938: Add e2e test to 4.9 branch 2021-12-13 19:07:55 UTC
Red Hat Product Errata RHBA-2021:5209 0 None None None 2022-01-05 16:12:15 UTC

Description OpenShift BugZilla Robot 2021-12-13 18:29:19 UTC
+++ This bug was initially created as a clone of Bug #2031854 +++

+++ This bug was initially created as a clone of Bug #2031826 +++

In some recently published z-stream releases of OCP, the driver-toolkit image contained the wrong kernel package versions. One measure we can take to avoid this going forward is to run an e2e test script against each nightly build of OCP to confirm the correct package versions are being installed.

To allow for customizations of the tests for certain releases, and to simplify the ci-operator configs, this e2e test script should be backported to 4.8, and a simple version of it should be added to 4.7.

Comment 2 Walid A. 2021-12-16 21:04:21 UTC
Verified:  the e2e test script is in the release-4.8 branch:

Comment 6 errata-xmlrpc 2022-01-05 16:12:09 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 (OpenShift Container Platform 4.8.25 bug fix 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.


Note You need to log in before you can comment on or make changes to this bug.