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 1519173

Summary: man page for nm-openvswitch states wrong device type
Product: Red Hat Enterprise Linux 7 Reporter: Vladimir Benes <vbenes>
Component: NetworkManagerAssignee: Lubomir Rintel <lrintel>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.5CC: atragler, bgalvani, fgiudici, lrintel, rkhan, sukulkar, thaller
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.12.0-0.1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 11:11:02 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 Vladimir Benes 2017-11-30 10:41:12 UTC 
Description of problem:
nmcli conn add conn.type ethernet conn.interface eth0 conn.master port1

this should be type ethernet or conn.type 802-3-ethernet

Version-Release number of selected component (if applicable):
1.10
Comment 1 Beniamino Galvani 2018-04-10 07:38:12 UTC 
'type' is an alias of 'connection.type' and both should accept either '802-3-ethernet' or 'ethernet'. The nmcli man page confirms this:

   add [save {yes | no}] {option value | [+|-]setting.property value}...

    ...
    To construct a meaningful connection you at the very least need to set the connection.type property (or use the type alias) to one of known NetworkManager connection types:

    ·   ethernet
    ·   wifi

But they are not actually equivalent:

 $ nmcli connection add type ethernet ifname eth0
 Connection 'ethernet-eth0' (714b5976-8f84-499d-9a3a-f25453ab55ff) successfully added.

 $ nmcli connection add conn.type ethernet ifname eth0
 Error: invalid connection type; ethernet.

I think this is a bug, the second command should work as well.
Comment 2 Lubomir Rintel 2018-08-06 12:11:26 UTC 
Fixed in 1.11.1-dev-381-g6713ab4d6c, went in with 1.12 rebase.
Comment 4 Vladimir Benes 2018-08-21 13:27:54 UTC 
Fixed to show correctly:
$ nmcli conn add type ethernet conn.interface eth0 conn.master port1
Connection 'ovs-slave-eth0' (d459c45c-cf78-4c1c-b4b7-505e71379624) successfully added.
Comment 6 errata-xmlrpc 2018-10-30 11:11:02 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:3207