Bug 1979738 - driver-toolkit gcc install unable to download extract-vmlinux script in ART builds
Summary: driver-toolkit gcc install unable to download extract-vmlinux script in ART b...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Special Resource Operator
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.9.0
Assignee: dagray
QA Contact: Lena Horsley
URL:
Whiteboard:
Depends On:
Blocks: 1979984
TreeView+ depends on / blocked
 
Reported: 2021-07-06 21:39 UTC by dagray
Modified: 2021-10-18 17:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 17:38:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift driver-toolkit pull 47 0 None open Bug 1979738: Remove curl of extract-vmlinux 2021-07-06 21:46:56 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:38:16 UTC

Description dagray 2021-07-06 21:39:46 UTC
The driver-toolkit container build tries to curl the extract-vmlinux script, which does not work in the (disconnected) ART build environment. This script is available as part of the kernel packages already installed in the location /usr/src/kernels/${INSTALLED_KERNEL}/scripts/extract-vmlinux, at least on the architectures for which the script will work.

In the other architectures, we can just install whichever gcc version is available by default in the ART builds.

This is needed in order for force the driver-toolkit to install the specific gcc version which was used to compile the kernel in the driver-toolkit.

Comment 2 Lena Horsley 2021-07-15 18:49:08 UTC
Verified in build: 4.9.0-0.nightly-2021-07-15-015134

1. Go to the OpenShift release nightly build page for the nightly build, click "Download the installer," and then click "release.txt."

2. Search for "driver-toolkit" and pull the corresponding image to your dev machine with the command:
podman pull --authfile /path/to/pullsecret <openshift_release_repo>/<corresponding_image_to_your_dev_machine>

3. Enter the following command from the terminal: 
podman run <image_from_previous_step> cat /tmp/kernel_info | grep -Eo "gcc version ([0-9\.]+)" | grep -Eo "([0-9\.]+)"

4. Enter the following command from the terminal:
podman run <image_from_previous_step> dnf list installed | grep gcc

5. Ensure that the output from step 3 matches the installed version of gcc from step 4


==================================================================
Output:
Step 3:  
8.4.1


Step 4: 
gcc.x86_64                                    8.4.1-1.el8                          @rhel-8-appstream-rpms-x86_64
libgcc.x86_64                                 8.4.1-1.el8                          @System

Comment 5 errata-xmlrpc 2021-10-18 17:38:02 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.9.0 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:3759


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