Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2062352

Summary: [4.8.z] [tracker] nf_reinject calls nf_queue_entry_free on an already freed entry->state
Product: OpenShift Container Platform Reporter: Micah Abbott <miabbott>
Component: RHCOSAssignee: Micah Abbott <miabbott>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Nguyen <mnguyen>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.7CC: adsoni, dornelas, ekovsky, jdesousa, jkaur, jligon, mbagga, miabbott, mnguyen, mrussell, nsharma, nstielau, peli, rbolling, rhcos-triage, travier, vagrawal
Target Milestone: ---   
Target Release: 4.8.z   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2062351
: 2062354 (view as bug list) Environment:
Last Closed: 2022-05-06 14:54:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2054705, 2061445, 2062349, 2062351    
Bug Blocks: 2062354    

Comment 3 Micah Abbott 2022-04-22 16:27:56 UTC
The dependent RHEL BZ (https://bugzilla.redhat.com/show_bug.cgi?id=2061445) was fixed as part of https://access.redhat.com/errata/RHSA-2022:1455

That errata included kernel-4.18.0-305.45.1.el8_4 which was included in RHCOS 48.84.202204202010-0

This build of RHCOS (or newer) should appear in OCP 4.8.z within the next 1-2 weeks.

Comment 5 Michael Nguyen 2022-04-27 13:32:39 UTC
Verified the fixed kernel is in RHCOS 48.84.202204251538-0 which is a part of OCP 4.8.0-0.nightly-2022-04-26-191618

$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.8.0-0.nightly-2022-04-26-191618   True        False         28s     Cluster version is 4.8.0-0.nightly-2022-04-26-191618
$ oc get node
NAME                                       STATUS   ROLES    AGE   VERSION
ci-ln-wmklc82-72292-zlg9c-master-0         Ready    master   21m   v1.21.8+ed4d8fd
ci-ln-wmklc82-72292-zlg9c-master-1         Ready    master   21m   v1.21.8+ed4d8fd
ci-ln-wmklc82-72292-zlg9c-master-2         Ready    master   21m   v1.21.8+ed4d8fd
ci-ln-wmklc82-72292-zlg9c-worker-a-qzjgk   Ready    worker   13m   v1.21.8+ed4d8fd
ci-ln-wmklc82-72292-zlg9c-worker-b-z6l6t   Ready    worker   13m   v1.21.8+ed4d8fd
ci-ln-wmklc82-72292-zlg9c-worker-c-4hz2v   Ready    worker   13m   v1.21.8+ed4d8fd
$ oc debug node/ci-ln-wmklc82-72292-zlg9c-worker-a-qzjgk
Starting pod/ci-ln-wmklc82-72292-zlg9c-worker-a-qzjgk-debug ...
To use host binaries, run `chroot /host`
Pod IP: 10.0.128.2
If you don't see a command prompt, try pressing enter.
sh-4.4# chroot /host
sh-4.4# rpm-ostree status
State: idle
Deployments:
* pivot://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:6e661713d2bd5ec3a1a3204900a65ababf7567cc6d24d65b906c50d1f491f4ec
              CustomOrigin: Managed by machine-config-operator
                   Version: 48.84.202204251538-0 (2022-04-25T15:41:18Z)

  ostree://13c18da5e6fee09fade484c3903209730cbb73e9ebcab806b9e9000cf97fd719
                   Version: 48.84.202109241901-0 (2021-09-24T19:04:29Z)
sh-4.4# rpm -q kernel
kernel-4.18.0-305.45.1.el8_4.x86_64

Comment 7 Micah Abbott 2022-05-02 20:53:46 UTC
This BZ was mistakenly omitted from the advisory for OCP 4.8.39, however the fixed kernel was included in the RHCOS build as part of OCP 4.8.39

If we inspect the labels on the `machine-os-content` from the 4.8.39 payload, we have recorded the version of the kernel included in RHCOS:


```
$ oc image info -o json $(oc adm release info --image-for=machine-os-content quay.io/openshift-release-dev/ocp-release:4.8.39-x86_64) | jq '.config.config.Labels["com.coreos.rpm.kernel"]'
"4.18.0-305.45.1.el8_4.x86_64"
```

This matches the version of the `kernel` found in https://access.redhat.com/errata/RHSA-2022:1455

Comment 10 Micah Abbott 2022-05-03 14:57:03 UTC
(In reply to peli from comment #8)

> Thank you very much for clarifying this. Is it possible to amend the
> advisory? If not, do we have any option to have a public customer
> communication note about this?

It's not possible to amend advisories once they have been shipped live.

> Can you please redirect us to the RHBA so that we can update the same to the CU to upgrade their cluster?

I'm not certain which RHBA you are referring to.  There are a number of advisories attached to the 4.8.39 release:

https://access.redhat.com/errata/product/290/ver=4.8/rhel---8/x86_64/RHBA-2022:1429
https://access.redhat.com/errata/product/290/ver=4.8/rhel---8/x86_64/RHBA-2022:1427
https://access.redhat.com/errata/product/290/ver=4.8/rhel---8/x86_64/RHBA-2022:1423
https://access.redhat.com/errata/product/290/ver=4.8/rhel---8/x86_64/RHBA-2022:1430