MOS 5.1.1: keystone container can't start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Alexander Makarov |
Bug Description
This issue was found by BVT tests for checks new packages for stable repository.
Durring the automated tests we can see errors with connectivity to keystone endpoint:
2014-11-10 12:15:31,142 - WARNING http.py:47 -- Cant establish connection to keystone with url http://
2014-11-10 12:15:31,157 - WARNING http.py:95 -- Authorization failure: Authentication required
2014-11-10 12:15:31,158 - INFO http.py:37 -- Initialize keystoneclient with url http://
2014-11-10 12:15:31,161 - WARNING http.py:47 -- Cant establish connection to keystone with url http://
example:
http://
Steps To Reproduce:
1. Deploy Fuel main node.
2. Check keystone container.
Observed Result:
Keystone container can't start:
___________________
[root@nailgun ~]# dockerctl start keystone
Error: Cannot start container fuel-core-
2014/11/10 12:24:12 Error: failed to start one or more containers
checking container keystone
No defined test for determining if keystone is ready.
keystone is ready.
___________________
[root@nailgun ~]# dockerctl restart keystone
Error: Cannot restart container fuel-core-
2014/11/10 12:24:37 Error: failed to restart one or more containers
___________________
In log file /var/log/
- - - - - - - - - -
No defined test for determining if keystone is ready.
keystone is ready.
Error: Cannot start container fuel-core-
2014/11/10 12:24:40 Error: failed to start one or more containers
Attaching to container fuel-core-
2014/11/10 12:24:40 You cannot attach to a stopped container, start it first
checking container keystone
No defined test for determining if keystone is ready.
keystone is ready.
Error: Cannot start container fuel-core-
2014/11/10 12:24:51 Error: failed to start one or more containers
Attaching to container fuel-core-
2014/11/10 12:24:51 You cannot attach to a stopped container, start it first
checking container keystone
No defined test for determining if keystone is ready.
keystone is ready.
Error: Cannot start container fuel-core-
2014/11/10 12:25:02 Error: failed to start one or more containers
Attaching to container fuel-core-
2014/11/10 12:25:02 You cannot attach to a stopped container, start it first
- - - - - - - - - -
Changed in fuel: | |
importance: | Undecided → Critical |
milestone: | none → 5.1.1 |
status: | New → Confirmed |
Changed in fuel: | |
assignee: | nobody → Fuel Core Team (fuel-core) |
description: | updated |
Changed in fuel: | |
assignee: | Fuel Core Team (fuel-core) → MOS Keystone (mos-keystone) |
Changed in fuel: | |
assignee: | MOS Keystone (mos-keystone) → Alexander Makarov (amakarov) |
status: | Confirmed → In Progress |
Changed in fuel: | |
status: | In Progress → Fix Committed |
It looks like keystone is missing pbr.version in requirements: main]/Keystone/ Exec[keystone- manage db_sync]/returns: Traceback (most recent call last): main]/Keystone/ Exec[keystone- manage db_sync]/returns: File "/usr/bin/ keystone- manage" , line 37, in <module> main]/Keystone/ Exec[keystone- manage db_sync]/returns: from keystone import cli main]/Keystone/ Exec[keystone- manage db_sync]/returns: File "/usr/lib/ python2. 6/site- packages/ keystone/ cli.py" , line 20, in <module> main]/Keystone/ Exec[keystone- manage db_sync]/returns: import pbr.version main]/Keystone/ Exec[keystone- manage db_sync]/returns: ImportError: No module named pbr.version
Notice: /Stage[
Notice: /Stage[
Notice: /Stage[
Notice: /Stage[
Notice: /Stage[
Notice: /Stage[
Error: keystone-manage db_sync returned 1 instead of one of [0]
Passing to mos-keystone to fix spec for python-pbr dependency