This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2158708 - [NMCI] strange delays after * Reboot step in NMCI
Summary: [NMCI] strange delays after * Reboot step in NMCI
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.8
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: rc
: ---
Assignee: NetworkManager Development Team
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-06 08:52 UTC by Vladimir Benes
Modified: 2023-08-17 09:23 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-17 09:23:26 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-29 0 None None None 2023-01-22 10:48:22 UTC
Red Hat Issue Tracker   RHEL-1400 0 None None None 2023-08-17 09:23:25 UTC
Red Hat Issue Tracker RHELPLAN-144093 0 None None None 2023-01-06 08:57:23 UTC

Description Vladimir Benes 2023-01-06 08:52:17 UTC
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

Comment 2 RHEL Program Management 2023-08-17 09:22:26 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.