Use placement version allowing re-parenting RP update

That is microversion 1.37.

The next time a placement re-sync is triggered (for example by
restarting the respective agents) this corrects the parents
of wrongly created resource providers introduced by bug #1921150.

Change-Id: I6b54aa9c21bf28de1d451c195e37efde6110258a
Depends-On: https://review.opendev.org/c/openstack/placement/+/784020
Related-Bug: #1921150
This commit is contained in:
Bence Romsics 2021-04-07 13:35:18 +02:00 committed by Rodolfo Alonso
parent 6fc30ae5ed
commit 270184e936
2 changed files with 16 additions and 1 deletions

View File

@ -39,7 +39,8 @@ PLACEMENT_API_WITH_NESTED_RESOURCES = 'placement 1.14'
PLACEMENT_API_RETURN_PROVIDER_BODY = 'placement 1.20'
PLACEMENT_API_ERROR_CODE = 'placement 1.23'
PLACEMENT_API_CONSUMER_GENERATION = 'placement 1.28'
PLACEMENT_API_LATEST_SUPPORTED = PLACEMENT_API_CONSUMER_GENERATION
PLACEMENT_API_UPDATE_REPARENT = 'placement 1.37'
PLACEMENT_API_LATEST_SUPPORTED = PLACEMENT_API_UPDATE_REPARENT
GENERATION_CONFLICT_RETRIES = 10

View File

@ -0,0 +1,14 @@
---
upgrade:
- |
If you leave a long time window between upgrading Placement and Neutron
Server, then it is recommended to upgrade Placement first (as was always
the logical order since Neutron is a client of Placement).
If the window between upgrading Neutron and Placement is short - that is
no changes in (segments of routed networks and QoS) resources backed by
Placement during this window you can ignore this note.
fixes:
- |
Switched to using placement microversion 1.37 therefore we can fix the
resource provider tree corrupted by bug
https://launchpad.net/bugs/1921150.