yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1228331] Re: nova-consoleauth ignores conductor setting

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Russell Bryant <1228331@xxxxxxxxxxxxxxxxxx>
Date: Fri, 04 Oct 2013 19:57:28 -0000
Reply-to: Bug 1228331 <1228331@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Should be fixed already

commit 13a6574987ee91068ffc46f2653256c57e86cced
Author: Russell Bryant <rbryant@xxxxxxxxxx>
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


** Changed in: nova
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1228331

Title:
  nova-consoleauth ignores conductor setting

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  if you have set
  [conductor]
  use_local=true

  in nova.conf, nova-consoleauth ignores this and continues to call
  conductor

  2013-09-20 18:31:50.836 DEBUG nova.openstack.common.rpc.amqp [req-
  4ee46e9d-6c95-43d3-88de-5f5548b2b17e None None] Making synchronous
  call on conductor ... multicall /usr/lib/python2.7/dist-
  packages/nova/openstack/common/rpc/amqp.py:583

  This causes VNC consoles to fail.
  This is easily fixed by just installing and starting nova-conductor, but, why offer the option to disable, if not everything will honor it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1228331/+subscriptions