Public bug reported:
If we use --config-drive=True via client we'll have filled config_drive
column in db. In the other hand if we use force_config_drive=True in
nova.conf the column will be empty. Also, in both cases config drive
will be attached to vm, and I can't find any problems with live-
migration or evacuation. In my deployment I use shared storage.
** 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/1303714
Title:
force_config_drive=True don't go to db
Status in OpenStack Compute (Nova):
New
Bug description:
If we use --config-drive=True via client we'll have filled
config_drive column in db. In the other hand if we use
force_config_drive=True in nova.conf the column will be empty. Also,
in both cases config drive will be attached to vm, and I can't find
any problems with live-migration or evacuation. In my deployment I use
shared storage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1303714/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
