Bug 2178269 - [NMCI] preserve_master_and_ip_settings test fail
Summary: [NMCI] preserve_master_and_ip_settings test fail
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: NetworkManager
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: NetworkManager Development Team
QA Contact: Vladimir Benes
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-14 17:15 UTC by Vladimir Benes
Modified: 2023-07-13 07:25 UTC (History)
7 users (show)

Fixed In Version: NetworkManager-1.43.6-1.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-385 0 None None None 2023-03-14 17:16:13 UTC
Red Hat Issue Tracker RHELPLAN-151810 0 None None None 2023-03-14 17:16:16 UTC
freedesktop.org Gitlab NetworkManager NetworkManager-ci merge_requests 1409 0 None opened tuntap: add 1.43.6+ preserve_master_and_ip_settings 2023-04-28 12:58:49 UTC
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 1599 0 None merged device: stop activation when queueing the unmanaged state 2023-04-11 07:20:48 UTC

Description Vladimir Benes 2023-03-14 17:15:38 UTC 
Description of problem:
we can still see a failure in preserve_master_and_ip_settings test from NMCI

log attached

Version-Release number of selected component (if applicable):
NetworkManager-1.40.16-1.el8.x86_64
but 
1.43.3 as well
and older as well visible since 1.36 (but not in 1.34.x)


How reproducible:
not sure

Steps to Reproduce:
1. we can see that in NMCI from time to time, adding a workaround with one more `ip up` command and checking whether the assumed connection is there rather than not.
Comment 6 Vladimir Benes 2023-04-28 12:58:49 UTC 
1.43.6+ preserve_master_and_ip_settings introduced. Running 200 times w/o any issues.
Note You need to log in before you can comment on or make changes to this bug.