[Bug 1081836] Re: nova-compute (folsom) fails to start, compute_driver is None

[OpenStack Hudson]

Reviewed:  https://review.openstack.org/16711
Committed: http://github.com/openstack/nova/commit/7e8a1662577bc86e873f9f957e74076ac89eb80b
Submitter: Jenkins
Branch:    stable/folsom

commit 7e8a1662577bc86e873f9f957e74076ac89eb80b
Author: Adam Gandelman <adam.gandelman at canonical.com>
Date:   Wed Nov 21 16:13:29 2012 -0800

    Reinstate default FLAGS.compute_driver for folsom
    
    A previous cherry-picked commit moved the compute_driver flag from
    the compute manager to the global flags file, but did not take the
    flags default value along.  This breaks existing Folsom installations
    that still use connection_type.
    
    Note, this is only proposed to stable/folsom to fix a regression. Not
    applicable to master as connection_type is gone in Grizzly.
    
    Fixes bug 1081836.
    
    Change-Id: I135d6adc215c40fb9f46f382dbe22fb38b413ff8


** Changed in: nova/folsom
       Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1081836

Title:
  nova-compute (folsom) fails to start, compute_driver is None

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