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.

Description of problem:
When we use "ovs" as a device name while creating a linux bridge via ifcfg (with NetworkManager disabled) initscripts thinks we want to create an Open vSwitch device.

Version-Release number of selected component (if applicable):
both initscripts-9.49.30 and initscripts-9.65

How reproducible:
Always

Steps to Reproduce:
$ echo '\
DEVICE=ovs
TYPE=Bridge
ONBOOT=no
NM_CONTROLLED=no' > /etc/sysconfig/network-scripts/ifcfg-ovs
$ ifup ovs

Actual results:
Fails with "Invalid OVS interface type Bridge".

Expected results:
Create a linux bridge with name 'ovs'.

The problem is here:
https://github.com/fedora-sysv/initscripts/blob/master/sysconfig/network-scripts/network-functions#L117

There is no case for TYPE = Bridge
Since the bridge stuff is handled by the ifup-eth we could probably add case that  would assign it to "eth"

Problem is that bridging is not strictly limited to ethernet (see https://wiki.linuxfoundation.org/networking/bridge "What can be bridged?" ).
And in theory user could have its own special ifup-whatever for network that is not ethernet-based but also do bridging and have DEVICE=whatever1 Type=Bridge.

But this case is pretty unlikely.

*** Bug 1402267 has been marked as a duplicate of this bug. ***

Possible fix:

https://github.com/fedora-sysv/initscripts/pull/62

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.