Skip to content

BZ1918456 new changes #30285

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
StephenJamesSmith wants to merge 1 commit into from
Closed

BZ1918456 new changes #30285

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions release_notes/ocp-4-7-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2043,9 +2043,13 @@ $ oc patch route/canary -n openshift-ingress-canary -p '{"spec":{"tls":{"termina
+
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1932401[*BZ#1932401*])

* Updates to openvswitch ("net: openvswitch: reorder masks array based on usage") code causes the openvswitch et/openvswitch/flow_table::flow_lookup accessing per-cpu data condition on preemptible (and migratable) sections, leading to a real time kernel panic. As a result, the kernel-rt is unstable and will impact low latency applications.
* Updates to openvswitch ("net: openvswitch: reorder masks array based on usage") code, causes the openvswitch et/openvswitch/flow_table::flow_lookup accessing per-cpu data condition on preemptible (and migratable) sections, leading to a real time kernel panic. As a result, the kernel-rt is unstable and will impact low latency applications.
+
It is recommended not to upgrade to {product-title} 4.7 until this is fixed.
Customers who are using the kernel-rt and run either {product-title} 4.6 or 4.7.0 will experience a severe impact.
+
The impact is continuous. For example, if the customer is using the Precision Time Protocol (PTP), the daemon is unstable and the protocol faults every minute. A stable time synchronization is never achieved.
+
There is no remediation currently available.
+
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1918456[*BZ#1918456*])

Expand Down