yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #32652
[Bug 1430365] Re: config drive table force_config_drive parameter values do not match Impl
Not sure something needs to be fixed on Nova. Please change the status
back to New if you think yes and explain why.
** Changed in: nova
Status: New => Invalid
--
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/1430365
Title:
config drive table force_config_drive parameter values do not match
Impl
Status in OpenStack Compute (Nova):
Invalid
Status in OpenStack Manuals:
Confirmed
Bug description:
The config drive table [1] describes for the force_config_drive parameter the following options:
Default: None
Other Options: always
But looking at the code [2], only the following values are allowed:
always, True, False
What does the current default 'None' mean? Is it really a value? Or
desribes it the abscense of the parameter? I could not configure it
for the force_config_drive option. The abscense of the parameter is
the same as 'False', so I guess that's the correct default, isn't it?
The docs should be updated accordingly.
[1] https://github.com/openstack/openstack-manuals/blob/master/doc/common/tables/nova-configdrive.xml
[2] https://github.com/openstack/nova/blob/master/nova/virt/configdrive.py
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1430365/+subscriptions