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.

Bug 2065637

Summary: Snapshot rollback does not respect managed no set by nmcli
Product: Red Hat Enterprise Linux 8 Reporter: Filip Pokryvka <fpokryvk>
Component: NetworkManagerAssignee: NetworkManager Development Team <nm-team>
Status: CLOSED MIGRATED QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.6CC: bgalvani, lrintel, rkhan, sfaye, sukulkar, till
Target Milestone: rcKeywords: MigratedToJIRA, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-16 19:42:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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)