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 2065637 - Snapshot rollback does not respect managed no set by nmcli
Summary: Snapshot rollback does not respect managed no set by nmcli
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: NetworkManager Development Team
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-18 11:42 UTC by Filip Pokryvka
Modified: 2023-08-16 19:42 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-16 19:42:05 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-669 0 None None None 2023-07-13 07:25:44 UTC
Red Hat Issue Tracker   RHEL-1393 0 None None None 2023-08-16 19:42:05 UTC
Red Hat Issue Tracker RHELPLAN-116102 0 None None None 2022-03-18 11:45:19 UTC

Description Filip Pokryvka 2022-03-18 11:42:58 UTC 
Description of problem:
There are following two runs of the test libnm_snapshot_reattach_unmanaged_ports_to_bridge, once device is set unmanaged by udev [1], and once it is additionally set unmanaged by `nmcli dev set portXb managed no` [2]. [1] serves as valid reproducer for bz2035519, but unmanaging device by nmcli makes the test pass (that command should have no effect).  

Version-Release number of selected component (if applicable):
1.36.0-2.el8

How reproducible:
always

Steps to Reproduce:
1. run the test libnm_snapshot_reattach_unmanaged_ports_to_bridge
2. uncoment test lines to unmanage ports via nmcli
3. run the test again

Actual results:
step 1. is failing, while step 3. is passing, but 2. should have no effect as device is already unmanaged

Expected results:
Both should fail on affected version, or both should pass on fixed version

Additional info:
[1] https://tools.dqe.lab.eng.bos.redhat.com/fpokryvk/reports/report_NetworkManager-ci_Test0_libnm_snapshot_reattach_unmanaged_ports_to_bridge.html
[2] https://tools.dqe.lab.eng.bos.redhat.com/fpokryvk/reports/report_NetworkManager-ci_Test0_libnm_snapshot_reattach_unmanaged_ports_to_bridge_managed_no.html

(reports are from rhel9, but the same results on rhel8)
Note You need to log in before you can comment on or make changes to this bug.