Ask Your Question

nova-status upgrade check fail

asked 2017-06-22 01:33:21 -0600

vicky yy gravatar image

updated 2017-06-23 00:26:13 -0600

Hello Everyone,

Nova installed according to :

nova-status upgrade check fail on compute node

Traceback (most recent call last):
  File "/bin/nova-status", line 10, in <module>
  File "/usr/lib/python2.7/site-packages/nova/cmd/", line 444, in main
  File "/usr/lib/python2.7/site-packages/nova/", line 52, in parse_args
  File "/usr/lib/python2.7/site-packages/oslo_config/", line 2359, in __call__
oslo_config.cfg.ConfigFilesPermissionDeniedError: Failed to open some config files: /usr/share/nova/nova-dist.conf,/etc/nova/nova.conf

use root in compute node:

[root@ocataCompute log]# nova-status upgrade check
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/nova/cmd/", line 456, in main
    ret = fn(*fn_args, **fn_kwargs)
  File "/usr/lib/python2.7/site-packages/nova/cmd/", line 386, in check
    result = func(self)
  File "/usr/lib/python2.7/site-packages/nova/cmd/", line 131, in _check_cellsv2
    meta.bind = db_session.get_api_engine()
  File "/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/", line 153, in get_api_engine
    return api_context_manager.get_legacy_facade().get_engine()
  File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/", line 707, in     get_legacy_facade
    return self._factory.get_legacy_facade()
  File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/", line 261, in     get_legacy_facade
  File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/", line 403, in _start
    engine_args, maker_args)
  File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/", line 425, in     _setup_for_connection
    "No sql_connection parameter is established")
CantStartEngineError: No sql_connection parameter is established

nova config:

sudo cat /etc/nova/nova.conf |grep -v ^# | grep -v ^$
firewall_driver = nova.virt.firewall.NoopFirewallDriver
use_neutron = True
my_ip =
transport_url = rabbit://openstack:rabbitpwd@ocataControl
enabled_apis = osapi_compute,metadata
auth_strategy = keystone
api_servers = http://ocataControl:9292
password = novapass
username = nova
project_name = service_test
user_domain_name = default
project_domain_name = default
auth_type = password
memcached_servers = ocataControl:11211
auth_url = http://ocataControl:35357
auth_uri = http://ocataControl:5000
lock_path = /var/lib/nova/tmp
auth_url = http://ocataControl:35357/v3
password = placementpass
username = placement
user_domain_name = Default
auth_type = password
project_name = service_test
project_domain_name = Default
os_region_name = RegionTWO
novncproxy_base_url = http://ocataControl:6080/vnc_auto.html
vncserver_proxyclient_address =
vncserver_listen =
enabled = True

The open_rc on compute node is below, no sure its enough.

export OS_USER_DOMAIN_NAME=Default
export OS_PROJECT_NAME=admin
export OS_USERNAME=admin
export OS_PASSWORD=adminpwd
export OS_AUTH_URL=http://ocataControl:35357/v3


cat /etc/httpd/conf.d/00-nova-placement-api.conf

Listen 8778

<VirtualHost *:8778>
    WSGIProcessGroup nova-placement-api
    WSGIApplicationGroup %{GLOBAL}
    WSGIPassAuthorization On
    WSGIDaemonProcess nova-placement-api processes=3 threads=1 user=nova group=nova
    WSGIScriptAlias / /usr/bin/nova-placement-api ...
edit retag flag offensive close merge delete


You probably need to be root? The program is unable to read nova.conf.

Bernd Bausch gravatar imageBernd Bausch ( 2017-06-22 04:08:14 -0600 )edit

reboot doesn't work, it seems like there is some config error, but I don't know where.

have no permission visit /usr/share/nova/nova-dist.conf seems odd

vicky yy gravatar imagevicky yy ( 2017-06-22 10:59:15 -0600 )edit

So what happens when you run sudo nova-status upgrade check? Or when you run the upgrade check after changing permissions on those files?

When you deploy OpenStack, you need to be root. So, it doesn't seem odd to me that you need to be root for the upgrade check.

Bernd Bausch gravatar imageBernd Bausch ( 2017-06-22 20:54:44 -0600 )edit

I haven't find a good log to describe this. nova-compute.log have no error. nova-status --log-file /var/log/nova/status.log upgrade check not work. any suggestion? thanks.

vicky yy gravatar imagevicky yy ( 2017-06-22 22:23:04 -0600 )edit

I think there is nothing in the logs because the command doesn't access any OpenStack service. My suggestion is to be superuser, because of this message:

ConfigFilesPermissionDeniedError: Failed to open some config files: /usr/share/nova/nova-dist.conf,/etc/nova/nova.conf.
Bernd Bausch gravatar imageBernd Bausch ( 2017-06-22 22:34:46 -0600 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2017-06-23 05:37:13 -0600

vicky yy gravatar image

Thanks Bernd,

nova-status upgrade check should run on control node with root priviages. Solve Problem.

edit flag offensive delete link more


I am getting similar issue now..Pasword is correct and with root access i am running.ANy suggestions

uday kiran reddy gravatar imageuday kiran reddy ( 2020-05-13 15:21:00 -0600 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2017-06-22 01:33:21 -0600

Seen: 3,950 times

Last updated: Jun 23 '17