Public bug reported:
If nova.conf doesn't exist in the typical location of
/etc/nova/nova.conf and OS_PLACEMENT_CONFIG_DIR isn't set, nova-
placement-api's wsgi application will fail. In our case with the
OpenStack snap, we have two possible paths we may pick nova.conf up
from, based on what --config-file specifies. I think the right answer
here is to be a bit more flexible and not set the default config file if
it's path doesn't exist.
** Affects: nova
Importance: Undecided
Assignee: Corey Bryant (corey.bryant)
Status: In Progress
** Affects: snap-nova
Importance: Undecided
Assignee: Corey Bryant (corey.bryant)
Status: New
** Also affects: snap-nova
Importance: Undecided
Status: New
** Changed in: snap-nova
Assignee: (unassigned) => Corey Bryant (corey.bryant)
** Changed in: nova
Assignee: (unassigned) => Corey Bryant (corey.bryant)
--
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/1696830
Title:
nova-placement-api default config files is too strict
Status in OpenStack Compute (nova):
In Progress
Status in Nova Snap:
New
Bug description:
If nova.conf doesn't exist in the typical location of
/etc/nova/nova.conf and OS_PLACEMENT_CONFIG_DIR isn't set, nova-
placement-api's wsgi application will fail. In our case with the
OpenStack snap, we have two possible paths we may pick nova.conf up
from, based on what --config-file specifies. I think the right answer
here is to be a bit more flexible and not set the default config file
if it's path doesn't exist.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1696830/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
