yahoo-eng-team team mailing list archive

[Matthew Gilliard <matthew.gilliard@xxxxxx>]

Public bug reported:

Default devstack install leaves

  force_config_drive = always

 in /etc/nova/nova.conf (slightly contradicting the docs:
http://docs.openstack.org/user-guide/content/enable_config_drive.html
which expects '.... = true')

An instance booted on this system does not have a config drive according
to 'nova show', and does not get an entry in the config_drive column of
the instances table. However the libvirt xml does show a config drive,
and of course it's visible on the instance.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1403889

Title:
  force_config_drive gives inconsistent instance state

Status in OpenStack Compute (Nova):
  New

Bug description:
  Default devstack install leaves

    force_config_drive = always

   in /etc/nova/nova.conf (slightly contradicting the docs:
  http://docs.openstack.org/user-guide/content/enable_config_drive.html
  which expects '.... = true')

  An instance booted on this system does not have a config drive
  according to 'nova show', and does not get an entry in the
  config_drive column of the instances table. However the libvirt xml
  does show a config drive, and of course it's visible on the instance.

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