config.json is missing from keystone container after restart of keystone container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Triaged
|
Medium
|
Kevin Carter |
Bug Description
Summary:
After deploying openstack stein (containerized) , a restart of the keystone containers on the overcloud controllers fails and the docker exits in status 2. The following error is seen below:
command: docker start keystone
docker logs keystone:
+ sudo -E kolla_set_configs
INFO:__
ERROR:_
Traceback (most recent call last):
File "/usr/local/
config = load_config()
File "/usr/local/
config = load_from_file()
File "/usr/local/
with open(config_file) as f:
IOError: [Errno 2] No such file or directory: '/var/lib/
docker ps -a | grep keystone shows the container exited (2).
"dumb-init --singl..." 3 hours ago Exited (2) 3 hours ago keystone
The config.json exists inside the container prior to the restart, but disappears completely after restart, resulting the error above.
Steps to reproduce:
1: Deploy Stein openstack containerized.
2: Restart keystone containers on overcloud controllers.
3: check the status of keystone container - in failed state.
Expected results:
Keystone container starts and remains healthy, which assumes the config.json exists in the container , in expected location of /var/lib/
The contents of config.json , which EXISTS before restarting keystone , contains:
()[root@
{
"command": "/usr/sbin/httpd",
"config_files": [
{
"dest": "/etc/keystone/
},
{
"dest": "/etc/httpd/
},
{
"dest": "/",
}
]
Environment:
Openstack Stein - tripleo deployment , containerized. Centos 7.7.1908
tags: | added: docker kolla |
Changed in tripleo: | |
milestone: | ussuri-3 → ussuri-rc3 |
Changed in tripleo: | |
milestone: | ussuri-rc3 → victoria-1 |
Changed in tripleo: | |
milestone: | victoria-1 → victoria-3 |
Have discovered that maybe there's a problem with our restart handler in ansible:
I have been using , to restart the container: container: 0.1:8787/ cbis/centos- binary- keystone: stein-latest
handlers:
- name: restart keystone
docker_
name: keystone
image: 172.31.
command: "kolla_start"
state: started
restart: yes
When I dont use the ansible module above, but instead use shell (below) for the same task, the config.json remains intact on the container and the container starts.
handlers:
- name: restart keystone
shell: "docker restart keystone"