Placement client isn't configured with region name
Bug #1836917 reported by
Pierre Riteau
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Blazar |
Fix Released
|
High
|
Pierre Riteau | ||
Stein |
Fix Committed
|
High
|
Pierre Riteau |
Bug Description
In multi-region deployments, placement operations can fail because the placement client used by Blazar isn't configured with the region name.
Changed in blazar: | |
importance: | Undecided → Critical |
importance: | Critical → High |
assignee: | nobody → Pierre Riteau (priteau) |
Changed in blazar: | |
milestone: | none → train-rc1 |
no longer affects: | blazar/train |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/671312 /git.openstack. org/cgit/ openstack/ blazar/ commit/ ?id=b366634af80 a3d400adf6e7bb9 d2dded64e10d75
Committed: https:/
Submitter: Zuul
Branch: master
commit b366634af80a3d4 00adf6e7bb9d2dd ed64e10d75
Author: Pierre Riteau <email address hidden>
Date: Wed Jul 17 16:50:32 2019 +0200
Fix placement operations in multi-region deployments
Change-Id: Ifc25d8a902d818 3266277586e4569 7052c46b550
Closes-Bug: #1836917