Neutron fails to create bandwidth providers if CONF.host is set
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Bence Romsics |
Bug Description
If neutron is configured to support qos minimum bandwidth policy rules and the [DEFAULT]/host config option is set for both nova-compute and neutron (sriov / ovs) agents on a given compute host then neutron fails to find the compute host root resource provider and therefore fails to create the agent providers and the device providers.
Reproduction:
* deploy an all-in-one devstack with the minimum bandwidth configuration [1] and set [DEFAULT]/host for nova-compute and neutron agent to something else than the hostname of the compute host.
* start up the nova and neutron services
* check what resource providers are created during the startup
Expected:
stack@aio:
+------
| uuid | name | generation |
+------
| 737d9a03-
| 31b21568-
| 1110cf59-
| 9734f92c-
+------
Actual:
stack@aio:
+------
| uuid | name | generation |
+------
| 737d9a03-
+------
There is the following log visible in the neturon-server:
Nov 22 11:39:34 aio neutron-
Nov 22 11:39:34 aio neutron-
Precieved severity:
* Medium, workaround exists: do not try to use qos configuration at the same time when the [DEFAULT]/host needs to be configured to other than the hostname of ht compute host.
Version: neutron from master 418be00155a9fa9
ML post about the problem and discussion about possible solution: http://
[1] https:/
description: | updated |
tags: | added: placement qos |
description: | updated |
Changed in neutron: | |
assignee: | nobody → Bence Romsics (bence-romsics) |
Changed in neutron: | |
importance: | Undecided → High |
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential |
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential |
Fix proposed to branch: master /review. opendev. org/696600
Review: https:/