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

Bug 2062351

Summary: [4.9.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 ERRATA QA Contact: Michael Nguyen <mnguyen>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.7CC: dornelas, ekovsky, jdesousa, jkaur, jligon, miabbott, mnguyen, mrussell, nsharma, nstielau, rbolling, rhcos-triage, travier
Target Milestone: ---   
Target Release: 4.9.z   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2062349
: 2062352 (view as bug list) Environment:
Last Closed: 2022-05-03 07:35:33 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    
Bug Blocks: 2062352, 2062354    

Comment 1 Micah Abbott 2022-04-22 16:27:01 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.9.z within the next 1-2 weeks.

Comment 2 Micah Abbott 2022-04-22 16:28:23 UTC
(In reply to Micah Abbott from comment #1)
> 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 should be RHCOS 49.84.202204201847-0

Comment 5 Michael Nguyen 2022-04-27 14:00:52 UTC
Verified the fixed kernel has been included in RHCOS 49.84.202204251501-0 which is part of  OCP 4.9.0-0.nightly-2022-04-27-100704

$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.9.0-0.nightly-2022-04-27-100704   True        False         46s     Cluster version is 4.9.0-0.nightly-2022-04-27-100704
$ oc get nodes
NAME                                       STATUS   ROLES    AGE     VERSION
ci-ln-qc7k4sk-72292-722bs-master-0         Ready    master   15m     v1.22.8+c02bd9d
ci-ln-qc7k4sk-72292-722bs-master-1         Ready    master   15m     v1.22.8+c02bd9d
ci-ln-qc7k4sk-72292-722bs-master-2         Ready    master   15m     v1.22.8+c02bd9d
ci-ln-qc7k4sk-72292-722bs-worker-a-4qs88   Ready    worker   9m2s    v1.22.8+c02bd9d
ci-ln-qc7k4sk-72292-722bs-worker-b-krcnb   Ready    worker   9m3s    v1.22.8+c02bd9d
ci-ln-qc7k4sk-72292-722bs-worker-c-qnc4b   Ready    worker   7m47s   v1.22.8+c02bd9d
$ oc debug node/ci-ln-qc7k4sk-72292-722bs-worker-a-4qs88
Starting pod/ci-ln-qc7k4sk-72292-722bs-worker-a-4qs88-debug ...
To use host binaries, run `chroot /host`
Pod IP: 10.0.128.3
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:d98cb7fe51f82a5eedce8ca8dd1a3a65406f15d13a40435786646148517392f3
              CustomOrigin: Managed by machine-config-operator
                   Version: 49.84.202204251501-0 (2022-04-25T15:04:32Z)

  ostree://3093d4596a48e37c9926dc53240af084c077e3bf2063ef2a8d8a81421b6e9987
                   Version: 49.84.202110081407-0 (2021-10-08T14:10:58Z)
sh-4.4# rpm -q kernel
kernel-4.18.0-305.45.1.el8_4.x86_64

Comment 7 errata-xmlrpc 2022-05-03 07:35:33 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.9.31 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.

https://access.redhat.com/errata/RHBA-2022:1605