Blazar

Placement client isn't configured with region name

  1. Series stein
  2. Bug #1836917
Bug #1836917 reported by Pierre Riteau
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Blazar
Fix Released
High
Pierre Riteau
Blazar train-rc1
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.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to blazar (master)

Reviewed: https://review.opendev.org/671312
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=b366634af80a3d400adf6e7bb9d2dded64e10d75
Submitter: Zuul
Branch: master

commit b366634af80a3d400adf6e7bb9d2dded64e10d75
Author: Pierre Riteau <email address hidden>
Date: Wed Jul 17 16:50:32 2019 +0200

    Fix placement operations in multi-region deployments

    Change-Id: Ifc25d8a902d8183266277586e45697052c46b550
    Closes-Bug: #1836917

Changed in blazar:
status: New → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to blazar (master)

Reviewed: https://review.opendev.org/679890
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=fedc28905907d4056b513a09645b4b5bf922d8f9
Submitter: Zuul
Branch: master

commit fedc28905907d4056b513a09645b4b5bf922d8f9
Author: Tetsuro Nakamura <email address hidden>
Date: Sat Aug 31 13:33:09 2019 +0000

    Fix gate issue of placement unit test

    The commit b366634af80a3d400adf6e7bb9d2dded64e10d75 changed the
    placement client to add "region_name" to "endpoint filter",
    but the unit test has not been changed and started to raise
    failures on gate.

    This patch fixes the issue.

    Change-Id: I6acafaca389261ea76f064092b8c32bcfb4108e1
    Related-Bug: #1836917

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/blazar 4.0.0.0rc1

This issue was fixed in the openstack/blazar 4.0.0.0rc1 release candidate.

Pierre Riteau (priteau)
Changed in blazar:
importance: Undecided → Critical
importance: Critical → High
assignee: nobody → Pierre Riteau (priteau)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to blazar (stable/stein)

Fix proposed to branch: stable/stein
Review: https://review.opendev.org/701529

Pierre Riteau (priteau)
Changed in blazar:
milestone: none → train-rc1
no longer affects: blazar/train
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to blazar (stable/stein)

Reviewed: https://review.opendev.org/701529
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=f1551cd6a3f32434166907bb6c77a063a6e14928
Submitter: Zuul
Branch: stable/stein

commit f1551cd6a3f32434166907bb6c77a063a6e14928
Author: Pierre Riteau <email address hidden>
Date: Wed Jul 17 16:50:32 2019 +0200

    Fix placement operations in multi-region deployments

    Change-Id: Ifc25d8a902d8183266277586e45697052c46b550
    Closes-Bug: #1836917
    (cherry picked from commit b366634af80a3d400adf6e7bb9d2dded64e10d75)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.