RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Can you please provide a full log at TRACE level? Thanks.

excellent news.
Are we ready to share instructions and new Network manager for them to try?

OK.
So what is the target z-stream release of 4.12 for it?

Definitely Mavenir.
Not 100% sure which end Telco customer.
But this is needed for joint validated RA with them.

We need this in RHEL 8.6 to line up to OCP 4.12 z-stream release.

(In reply to Arkady Kanevsky from comment #49)
> We need this in RHEL 8.6 to line up to OCP 4.12 z-stream release.

It is already part of the next RHEL 8.6 zstream batch as tracked in bug 2174363

Thanks Till. What is the timeline for it?

There's also now https://docs.openshift.com/container-platform/4.12/post_installation_configuration/coreos-layering.html#coreos-layering for the customer to roll out hotfixes exactly like this in a much more cluster-native way.

right. But image layering is still a tech preview in OCP 4.12.
so each one will require exception for use image layering and then another one for hot fix.

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 (NetworkManager bug fix and enhancement 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-2023:2968