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 2056386 - Failed to configure IPv4 and IPv6 types in Bond: NM always rolls back to previous checkpoint
Summary: Failed to configure IPv4 and IPv6 types in Bond: NM always rolls back to prev...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cockpit
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: 8.6
Assignee: Marius Vollmer
QA Contact: peyu
URL:
Whiteboard:
: 2056362 2056446 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-21 06:38 UTC by peyu
Modified: 2022-05-10 16:30 UTC (History)
12 users (show)

Fixed In Version: cockpit-264-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-10 15:18:39 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-112924 0 None None None 2022-02-21 14:07:33 UTC
Red Hat Product Errata RHSA-2022:2008 0 None None None 2022-05-10 15:18:42 UTC

Description peyu 2022-02-21 06:38:20 UTC 
Login cockpit, create bond through cockpit, configure Bond's IPv4 and IPv6 to other types than the default types. The setting does not take effect and will return to "Automatic" mode immediately.


Version-Release number of selected component (if applicable):
RHVH: rhvh-4.5.0.2-0.20220216.0+1

subscription-manager-cockpit-1.28.25-1.el8.noarch
cockpit-bridge-261-1.el8.x86_64
cockpit-system-261-1.el8.noarch
cockpit-storaged-261-1.el8.noarch
cockpit-ws-261-1.el8.x86_64
cockpit-261-1.el8.x86_64
cockpit-ovirt-dashboard-0.15.1-2.el8ev.noarch


How reproducible:
100%

Steps to Reproduce:
1. Install redhat-virtualization-host-4.5.0-202202161646_8.6
2. Login cockpit via Firefox browser
3. Go to "Networking" -> "Interfaces"
4. Click "Add bond", input bond name, mode and other information
5. Configure the Bond's IPv4 and IPv6 with other types than the default "Automatic"types
6. Click the "Change the settings" button in the "Connection will be lost" dialog that pops up
7. Check Bond's IPv4 and IPv6 types


Actual results:
1. The setting does not take effect and will return to "Automatic" mode immediately.


Expected results:
Configurations for Bond's IPv4 and IPv6 types should take effect 

Additional info:
Comment 1 Martin Pitt 2022-02-22 08:29:33 UTC 
This sounds very similar to bug 2056362. But unlike that, I can actually reproduce it with a bond. (Marius: Just our bog standard `./vm-run -s cockpit.socket rhel-8-6` in bots)

I see that NM rolls back to the old connection, even though I clicked on "keep connection":

  NetworkManager[884]: <info>  [1645518404.0318] checkpoint[0x55dbd109dc10]: rollback of /org/freedesktop/NetworkManager/Checkpoint/11

Note that there is a lot of SELinux noise in the logs, due to bug 2055199. But that's unrelated, `setenforce 0` does not change the behaviour.

Marius, can you please have a look?
Comment 2 Marius Vollmer 2022-02-22 12:53:04 UTC 
(In reply to Martin Pitt from comment #1)
> I see that NM rolls back to the old connection, even though I clicked on
> "keep connection":
> 
>   NetworkManager[884]: <info>  [1645518404.0318] checkpoint[0x55dbd109dc10]:
> rollback of /org/freedesktop/NetworkManager/Checkpoint/11

This is expected. The checkpoint is rolled back during the "Restoring connection" phase, and if you click "Keep connection" nothing more will be done.  Your changes have been undone and Cockpit is still connected to the server.

The checkpoint is always rolled back before we get the "Connection will be lost" dialog.  That dialog then gives you to choice to change settings anyway, without a checkpoint to protect you.
Comment 3 Marius Vollmer 2022-02-22 13:03:06 UTC 
> 7. Check Bond's IPv4 and IPv6 types

How did you check this exactly?  Cockpit itself is disconnected at this point and does no longer show correct information.  If you wait a bit, the network page will disappear completely and be replaced with a "Disconnected" screen.  (There is a "Reconnect" button but that wont work because there is no network connectivity any more.)

If I execute your steps, "nmcli con show bond0" on the machine itself shows the expected configuration.

> Expected results:
> Configurations for Bond's IPv4 and IPv6 types should take effect 

They do for me, but Cockpit does not always show them correctly because it has lost connection to the server at this point.
Comment 4 Marius Vollmer 2022-02-23 13:30:51 UTC 
Hmm, this is very likely also a instance of the bug fixed here: https://github.com/cockpit-project/cockpit/pull/17036

In my comments above, I had assumed that the connection will indeed be lost for real and I had only tested those scenarios. But reading the description more closely, the disconnection is probably not expected and the wrong behavior of Cockpit can indeed be explained by https://github.com/cockpit-project/cockpit/pull/17036.
Comment 6 Martin Pitt 2022-02-23 14:18:00 UTC 
Fix developed in https://github.com/cockpit-project/cockpit/pull/17036
Comment 7 Martin Pitt 2022-02-23 14:18:38 UTC 
*** Bug 2056362 has been marked as a duplicate of this bug. ***
Comment 9 Martin Pitt 2022-02-24 08:56:22 UTC 
*** Bug 2056446 has been marked as a duplicate of this bug. ***
Comment 10 Martin Pitt 2022-02-25 09:42:14 UTC 
This fix is verified through gating test.
Comment 16 errata-xmlrpc 2022-05-10 15:18:39 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: cockpit security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:2008
Note You need to log in before you can comment on or make changes to this bug.