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.

Requesting backport for upstream fix https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/403f207fe58538f0228ac42918f23d2e6a18e8b6


This bug was introduced in 1.18.0, and affects rhel-7.7.



This affects connection properties that don't have a default value of 0/FALSE/NULL. When trying to reset the value with nmcli, it was wrong.

For example 

  $ nmcli connection modify "$PROFILE" connection.autoconnect ''
  $ nmcli -f connection.autoconnect connection show "$PROFILE" 
  connection.autoconnect:                 no

  ("yes" would be correct).

  $ nmcli connection modify "$PROFILE" connection.autoconnect-retries ''
  $ nmcli -f connection.autoconnect-retries connection show "$PROFILE" 
  connection.autoconnect-retries:         0 (forever)

  (-1 would be correct).


The patch itself is trivial, hence I would fix this in rhel-7.7.

Resetting blocker per PM review. Will fix in 7.8.

-Sushil

also fixed on nm-1-18 branch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/2a2a66b4d5de87a73ea14c9e5d24963ae0eec236

We are checking that all values can be set now.. from 0 to 6. Test added.

(In reply to Vladimir Benes from comment #8)
> We are checking that all values can be set now.. from 0 to 6. Test added.

ah, the wrong bug, this one is about adding a test and verification of resetting values with an empty string. This is done and working well.

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, 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/RHBA-2020:1162