Ask Your Question
0

Openstack-Ansible - Problems after power failure

asked 2017-05-12 10:52:03 -0500

vgeorga gravatar image

Hello all,

About two months ago I had successfully installed OpenStack-Ansible on 3 nodes ( Controller, Compute, Storage) in a similar way to the official guide Appendix A test environment (https://docs.openstack.org/project-de...).

Unfortunately, there was a power outage last night so I had to cold start (power on) all nodes.

The problem that I am dealing with at the moment is that some of the containers are stopped and none of them has acquired any IP address like this:

NAME                                          STATE   AUTOSTART GROUPS            IPV4 IPV6 
infra1_cinder_api_container-0cf25d7d          RUNNING 1         onboot, openstack -    -    
infra1_cinder_scheduler_container-5807afd1    RUNNING 1         onboot, openstack -    -    
infra1_galera_container-cd218ab1              STOPPED 1         onboot, openstack -    -    
infra1_glance_container-6997e56e              RUNNING 1         onboot, openstack -    -    
infra1_heat_apis_container-8254d4ad           RUNNING 1         onboot, openstack -    -    
infra1_heat_engine_container-fea40a47         RUNNING 1         onboot, openstack -    -    
infra1_horizon_container-d91ec9a0             RUNNING 1         onboot, openstack -    -    
infra1_keystone_container-8e19d256            STOPPED 1         onboot, openstack -    -    
infra1_memcached_container-92f52215           RUNNING 1         onboot, openstack -    -    
infra1_neutron_agents_container-3f7b1d22      STOPPED 1         onboot, openstack -    -    
infra1_neutron_server_container-785f8d1e      RUNNING 1         onboot, openstack -    -    
infra1_nova_api_metadata_container-acd87f7f   STOPPED 1         onboot, openstack -    -    
infra1_nova_api_os_compute_container-164abcf2 STOPPED 1         onboot, openstack -    -    
infra1_nova_cert_container-18ab7444           STOPPED 1         onboot, openstack -    -    
infra1_nova_conductor_container-9e9a7e08      STOPPED 1         onboot, openstack -    -    
infra1_nova_console_container-613c6670        STOPPED 1         onboot, openstack -    -    
infra1_nova_scheduler_container-48c3ca53      STOPPED 1         onboot, openstack -    -    
infra1_rabbit_mq_container-d0c9f1cf           STOPPED 1         onboot, openstack -    -    
infra1_repo_container-0fd619c3                RUNNING 1         onboot, openstack -    -    
infra1_utility_container-508725a4             RUNNING 1         onboot, openstack -    -

Also, nothing seems to be working which I guess is caused from the keystone service being down.

Does anyone know a solution to this problem except for starting from scratch?

Thank you in advance for your help

V.G.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-05-16 12:52:38 -0500

vgeorga gravatar image

updated 2017-05-16 12:55:30 -0500

I found out that a possible solution to the container problem is the command issued below:

lxc-system-manage system-rebuild

This essentially reinitializes all the containers (interfaces,connections,services etc).

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

Stats

Asked: 2017-05-12 10:52:03 -0500

Seen: 148 times

Last updated: May 16 '17