Back to bug 1316730

Who When What Removed Added
Red Hat Bugzilla Rules Engine 2016-03-10 22:46:58 UTC Target Release --- 8.0
Angus Thomas 2016-03-22 17:54:06 UTC Status NEW ON_DEV
CC athomas
Assignee rhos-maint dsneddon
Keith Basil 2016-03-22 20:11:26 UTC CC kbasil
Keith Basil 2016-03-22 20:11:47 UTC Target Milestone --- ga
James Slagle 2016-03-28 11:01:53 UTC Status ON_DEV POST
Link ID OpenStack gerrit 291420
James Slagle 2016-03-28 15:59:22 UTC Status POST MODIFIED
Fixed In Version os-net-config-0.2.2-1.el7ost
errata-xmlrpc 2016-03-29 14:39:59 UTC Status MODIFIED ON_QA
Dan Sneddon 2016-03-31 17:34:08 UTC Doc Text Cause: When VLAN interfaces were placed directly on a Linux kernel bond, with no bridge, the VLANs may have been started before the bond.

Consequence: If the VLANs are started before the bond, then the physical interface will be down. This results in the VLAN failing to be started properly.

Fix: The os-net-config utility was updated so that it always starts bridges first, then bonds and interfaces, and finally VLANs.

Result: Starting the physical interfaces before the VLANs ensures that the physical network is up and available when the VLAN is started.
Arik Chernetsky 2016-04-03 12:41:21 UTC CC achernet
QA Contact yeylon oblaut
Ofer Blaut 2016-04-04 14:27:40 UTC CC dsneddon
Flags needinfo?(dsneddon)
Don Domingo 2016-04-06 04:30:17 UTC CC ddomingo
Doc Text Cause: When VLAN interfaces were placed directly on a Linux kernel bond, with no bridge, the VLANs may have been started before the bond.

Consequence: If the VLANs are started before the bond, then the physical interface will be down. This results in the VLAN failing to be started properly.

Fix: The os-net-config utility was updated so that it always starts bridges first, then bonds and interfaces, and finally VLANs.

Result: Starting the physical interfaces before the VLANs ensures that the physical network is up and available when the VLAN is started.
In previous releases, when VLAN interfaces were placed directly on a Linux kernel bond with no bridge, it was possible for the VLANs to start before the bond. When this occurred, the VLANs failed to start. With this release, the os-net-config utility now starts the physical network (namely, bridges first, then bonds and interfaces) before VLANs. This ensures that the VLANs have the interfaces necessary to start properly.
Ofer Blaut 2016-04-06 09:05:55 UTC Status ON_QA VERIFIED
Dan Sneddon 2016-04-06 20:56:50 UTC Flags needinfo?(dsneddon)
errata-xmlrpc 2016-04-07 14:24:18 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-04-07 21:49:19 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-04-07 17:49:19 UTC

Back to bug 1316730