NIC Partitioning shall work even if NetworkManager service is active
Bug #1807087 reported by
Karthik S
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Fix Released
|
Medium
|
Karthik S | ||
Bug Description
As of today, the NIC Partitioning feature requires the NetworkManager service to be disabled. When sriov_numvfs is written for the PF device by os-net-config the VF's are created. If NM is active, it tries to configure these VF's and in parallel os-net-config generates the ifcfg's for the VF's, runs ifup for those VF's. These 2 parallel contexts brings some inconsistency in the VF configuration and the ifup <ifcfg-vf> could fail.
Its identified that if the ifcfg for the PF is created with "NM_CONTROLLED=no", before writing the numvfs, then the above mentioned conflict does not occur
| Changed in tripleo: | |
| assignee: | nobody → Karthik S (ksundara) |
| status: | New → In Progress |
| Changed in tripleo: | |
| importance: | Undecided → Medium |
| milestone: | none → stein-2 |
| Changed in tripleo: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/os-net-config 10.2.0 | #1 |
| Changed in tripleo: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/os-net-config 9.3.0 | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/os-net-config 8.4.4 | #3 |
To post a comment you must log in.
This issue was fixed in the openstack/