OpenStack Compute (nova)

consoleauth services unnecessarily uses remote conductor

Bug #1190271 reported by Russell Bryant on 2013-06-12

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Compute (nova)	Fix Released	Medium	Russell Bryant	OpenStack Compute (nova) 2013.2 "havana"

Bug Description

As noted in the subject, unless you set use_local=True in your config, the consoleauth service will use the remote conductor service. There's no good reason for it to *ever* go remote, so we should force it to be local only.

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2013-06-12: Fix proposed to nova (master)

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

Changed in nova:
assignee:	nobody → Russell Bryant (russellb)
status:	New → In Progress

Mark McLoughlin (markmc) on 2013-07-08

Changed in nova:
importance:	Undecided → Medium

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2013-07-08: Fix merged to nova (master)

Reviewed: https://review.openstack.org/32748
Committed: http://github.com/openstack/nova/commit/13a6574987ee91068ffc46f2653256c57e86cced
Submitter: Jenkins
Branch: master

commit 13a6574987ee91068ffc46f2653256c57e86cced
Author: Russell Bryant <email address hidden>
Date: Fri Jul 5 14:59:13 2013 -0400

Remove conductor usage from consoleauth service

    There's no reason for the consoleauth service to use the conductor API
    since it is allowed to use the db directly. Remove the single conductor
    API call and replace it with the equivalent db call.

Fix bug 1190271.

Change-Id: Id6f50873f792ac4393dc2063f599f0418598091b