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 1492912 - Typo for AUTOCONNECT_SLAVES ifcfg entry in nm-settings-ifcfg-rh(5)
Summary: Typo for AUTOCONNECT_SLAVES ifcfg entry in nm-settings-ifcfg-rh(5)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.3
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-19 01:15 UTC by Dustin Black
Modified: 2018-04-10 13:30 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 13:29:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0778 0 None None None 2018-04-10 13:30:48 UTC

Description Dustin Black 2017-09-19 01:15:11 UTC 
The nm-settings-ifcfg-rh(5) has an incorrect key name for the NetworkManager ipv4.autoconnect-slaves features. In the man page this is shown with a dash as:

AUTOCONNECT-SLAVES

When the correct syntax is with an underscore as:

AUTOCONNECT_SLAVES


Incidentally, it is also unclear in the man page what values can be set in the ifcfg file for this option. It seems from my testing that this is a yes/no boolean in the ifcfg, while the ipv4.autoconnect-slaves option directly takes a 1/0 value.
Comment 2 Thomas Haller 2017-09-19 06:50:59 UTC 
fixed upstream: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=39d30a170dcb717d9c1dc980f0897d12f5c110f6

Thanks for reporting.


> Incidentally, it is also unclear in the man page what values can be set in the 
> ifcfg file for this option. It seems from my testing that this is a yes/no
> boolean in the ifcfg,

ifcfg-rh commonly accepts yes|true|1|no|false|0 for boolean values. That is the case for AUTOCONNECT_SLAVES as well. 

> while the ipv4.autoconnect-slaves option directly takes a 
> 1/0 value.

1/0 and -1. The property is an enum, -1 means default.

You don't say in which context:

 - nmcli (at least since 1.10) supports yes|1|no|0|default|-1.

  $ nmcli connection modify a connection.autoconnect-slaves x
  Error: failed to modify connection.autoconnect-slaves: invalid option 'x', use 
  one of [default,no,yes].

 - keyfile plugin only accepts numeric values for enum values.

 - on D-Bus, they are numeric as well.


for keyfile, ifcfg-rh and D-Bus, a missing key means "default|-1" as well.
Comment 4 Vladimir Benes 2017-12-04 14:38:50 UTC 
AUTOCONNECT-SLAVES not visible anymore
Comment 7 errata-xmlrpc 2018-04-10 13:29:44 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, 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-2018:0778
Note You need to log in before you can comment on or make changes to this bug.