Why does "placement status upgrad check" throw exception on Stein

asked 2019-09-06 13:05:02 -0500

Daryl gravatar image

updated 2019-09-06 13:05:58 -0500

I'm following the installation instructions at https://docs.openstack.org/placement/... and all appears to go smoothly. Then at the Verify step, the command "placement-status upgrade check" throws the following exception:

$ placement-status upgrade check
Traceback (most recent call last):
  File "/usr/bin/placement-status", line 10, in <module>
  File "/usr/lib/python3/dist-packages/placement/cmd/status.py", line 131, in main
    config(args=sys.argv[1:], project='placement')
  File "/usr/lib/python3/dist-packages/oslo_config/cfg.py", line 2127, in __call__
  File "/usr/lib/python3/dist-packages/oslo_config/cfg.py", line 2865, in _check_required_opts
    raise RequiredOptError(opt.name, group)
oslo_config.cfg.RequiredOptError: value required for option connection in group [placement_database]

I've scanned the [placement_database] section of placement.conf, and the only uncommented line is the 'connection' entry, which is exactly as specified in the installation documentation, except for my own password.

I am trying to upgrade from Queens on Ubuntu 16.0 to Stein on Ubuntu 18.04 and this is the first show-stopper I've encountered. Any help would be apprciated.

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2020-01-09 04:26:16 -0500

updated 2020-01-09 21:10:55 -0500

The command must be executed as root because the authority of /etc/placement is rwxr-x--- and other users do not have permission to enter the directory and so they can not find the placement.conf. This explains why: https://storyboard.openstack.org/#!/story/2006550 (https://storyboard.openstack.org/#!/s...)

edit flag offensive delete link more

answered 2019-09-07 06:25:02 -0500

cdent gravatar image

Since you're doing an upgrade rather than a clean install you may need some different steps, have a look at:



The error you're getting suggests that the command may not be looking at the configuration file you think it is. You can make it explicit by passing a "--config-file PATH" argument placement-status

edit flag offensive delete link more


Thanks, I'll have a look at that. However, this was not an upgrade in the normal sense of the word. The command was in the Verify step of a new install. By "upgrade" I meant that I had set my Queens install aside and started afresh with Stein. I could have done better with my choice of wording...

Daryl gravatar imageDaryl ( 2019-09-11 11:36:17 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2019-09-06 13:05:02 -0500

Seen: 483 times

Last updated: Jan 09