Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Following up to requests to fix this in 7.2.
As has been discussed previously (bug #1333983 comment #21), this is non-trivial and somewhat risky to backport to the 7.2 code base :(
Bronce, Yuri, I'd be very thankful if you could help me the use case, in particular the reason behind restarting NetworkManager. That way we could perhaps find an alternative solution/workaround.
(In reply to Lubomir Rintel from comment #3)
> Following up to requests to fix this in 7.2.
>
> As has been discussed previously (bug #1333983 comment #21), this is
> non-trivial and somewhat risky to backport to the 7.2 code base :(
>
> Bronce, Yuri, I'd be very thankful if you could help me the use case, in
> particular the reason behind restarting NetworkManager. That way we could
> perhaps find an alternative solution/workaround.
We use Cockpit to create basic networking on the host and then switch to use out host agent for day 2. The networking dies due to this issue. This is very severe.
(In reply to Yaniv Dary from comment #4)
> (In reply to Lubomir Rintel from comment #3)
> > Following up to requests to fix this in 7.2.
> >
> > As has been discussed previously (bug #1333983 comment #21), this is
> > non-trivial and somewhat risky to backport to the 7.2 code base :(
> >
> > Bronce, Yuri, I'd be very thankful if you could help me the use case, in
> > particular the reason behind restarting NetworkManager. That way we could
> > perhaps find an alternative solution/workaround.
>
> We use Cockpit to create basic networking on the host and then switch to use
> out host agent for day 2. The networking dies due to this issue. This is
> very severe.
Note that this is probably a different issue. The original bug report dealt with NetworkManager not being able to pick up a device on start when it lacked L3 configuration. The issue you're experiencing seems to be in the shutdown path.
I think the actual bug you're experiencing is tracked in bug #1371126