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.

Description of problem:
When we run tests with the Reboot step in NMCI it sometimes needs a second to be ready to run commands like nmcli device but in other cases, it needs 10+ seconds to be ready. We do run assert nmci.nmutil.start_NM_service(timeout=timeout), "NM start failed" to have this ready but this is not helping (and we had to bump timeout from 5 to 10s even for that)

I have a test case showing this when running in cycle stored in vb/failing_reboot (instruction how to run that are in commit message) 

Version-Release number of selected component (if applicable):
NetworkManager-1.40.9-31044.copr.63a8cec1b1.el9.x86_64

How reproducible:
randomly but usually we can see it in 200 runs 

Steps to Reproduce:
1. get NMCI 
2. test=test
3. a=0; while ./test_run.sh $test; do :; sleep 2;((a++)); echo "ATTEMPT $a"; if [ $a -eq 200 ]; then break; fi ; done; echo "ATTEMPT $a"


Actual results:
stability issues 

Expected results:
rock solid and quick service restarts

Additional info:
we probably need to report NM service as down and up after some checks are performed and we are sure other commands can run successfully

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.