Placement reporter service plugin sometimes creates orphaned resource providers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
Bence Romsics |
Bug Description
As discovered by lajoskatona while working on a fullstack test (https:/
$ openstack --os-placement-
+------
| uuid | name | generation | root_provider_uuid | parent_
+------
| 89ca1421-
| 4a6f5f40-
| 193134fd-
| dbc498c7-
| 4a8a819d-
| 1c7e83f0-
+------
Please note that all RPs should have the root_provider_uuid set to the devstack0 RP's uuid, but the open vswitch RPs have a different (wrong) root. And 'devstack0:Open vSwitch agent' has no parent.
This situation is dependent on service startup order. The ovs RPs were created before the compute host RP. That case should have been detected as an error, but it was not.
I'll upload a proposed fix right away.
tags: | added: stein-rc-potential |
Changed in neutron: | |
milestone: | none → stein-rc1 |
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential stein-rc-potential |
Fix proposed to branch: master /review. openstack. org/641034
Review: https:/