Ask Your Question

OpenStack services disabled on boot (Using RDO Packstack) : Queens Release

asked 2019-03-20 07:49:22 -0500

Sai gravatar image

I am installing OPenstack on Centos7 VM. I am installing Openstack using Packstack (Queens release). However, I am not able to bring up all the components. Some are "disabled on boot". When I do "openstack-services", the following comes up:

[root@localhost ~]# openstack-status == Nova services == openstack-nova-api: active

openstack-nova-compute: inactive (disabled on boot)

openstack-nova-network: inactive (disabled on boot)

openstack-nova-scheduler: active

openstack-nova-conductor: active

openstack-nova-console: inactive (disabled on boot)

openstack-nova-consoleauth: active

openstack-nova-xvpvncproxy: inactive (disabled on boot)

== Glance services ==

openstack-glance-api: active

openstack-glance-registry: active

== Keystone service ==

openstack-keystone: inactive (disabled on boot)

== Horizon service ==

openstack-dashboard: active

== neutron services ==

neutron-server: activating(disabled on boot)

neutron-dhcp-agent: active

neutron-l3-agent: active

neutron-metadata-agent: active

neutron-openvswitch-agent: active

neutron-metering-agent: active

== Cinder services ==

openstack-cinder-api: active

openstack-cinder-scheduler: active

openstack-cinder-volume: active

openstack-cinder-backup: active

== Ceilometer services ==

openstack-ceilometer-api: inactive (disabled on boot)

openstack-ceilometer-central: active

openstack-ceilometer-compute: inactive (disabled on boot)

openstack-ceilometer-collector: inactive (disabled on boot)

openstack-ceilometer-notification: inactive (disabled on boot)

== Support services ==

openvswitch: active

dbus: active

target: active

rabbitmq-server: failed

memcached: active

== Keystone users ==

Warning keystonerc not sourced

Please let me know what can be done to overcome this?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2019-03-20 19:03:34 -0500

updated 2019-03-20 19:20:07 -0500

If you provided details how exactly you created this cloud, I could give you a better answer with fewer assumptions.

You could enable the services: systemctl enable openstack-nova-compute etc. But many services are probably not supposed to be enabled anyway, such as openstack-nova-network or openstack-nova-xvpvncproxy. So my question is, do you have a problem with your cloud or are you only confused by the output of the openstack-services command?

Assuming an installation on a single server, openstack-nova-compute should be active. I don't know how reliable the openstack-services command is, so I would check if it really runs systemctl status openstack-nova-compute, and if not try starting it systemctl start openstack-nova-compute. If this fails, I would check for errors in the nova-compute log file.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2019-03-20 07:49:22 -0500

Seen: 20 times

Last updated: Mar 20