Placement API should be on controller nodes

Bug #1744112 reported by Ali Sanhaji
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-ovn
Fix Released
Undecided
Ali Sanhaji

Bug Description

Placement API is enabled on compute nodes in computenode-local.conf.sample, while it should be on the controller node. Use placement-client on devstack compute local.conf rather than enabling the API.

Changed in networking-ovn:
assignee: nobody → Ali Sanhaji (ali-sanhaji)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-ovn (master)

Fix proposed to branch: master
Review: https://review.openstack.org/535389

Changed in networking-ovn:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-ovn (master)

Reviewed: https://review.openstack.org/535389
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=c09722ba67bf3825637eb9d7b9bda81c9f14679e
Submitter: Zuul
Branch: master

commit c09722ba67bf3825637eb9d7b9bda81c9f14679e
Author: Ali Sanhaji <email address hidden>
Date: Thu Jan 18 16:46:18 2018 +0100

    Use placement-client rather than placement-api

    The Placement API runs on the controller, so placement-client should
    be used on the compute node.

    Change-Id: I872076ad639833c79faf0399f9b6ef533d73e709
    Closes-Bug: #1744112

Changed in networking-ovn:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/networking-ovn 4.0.0.0rc1

This issue was fixed in the openstack/networking-ovn 4.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/networking-ovn 5.0.0.0b1

This issue was fixed in the openstack/networking-ovn 5.0.0.0b1 development milestone.

tags: added: networking-ovn-proactive-backport-potential
tags: removed: networking-ovn-proactive-backport-potential
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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