[staging] Staging job master.staging.ubuntu.bvt_2 failed because of 401 errors during the fuel master node deployment

[Timur Nurlygayanov]

Failed Job:
http://jenkins-product.srt.mirantis.net:8080/view/Staging%20Mirrors/job/master.staging.ubuntu.bvt_2/60/consoleFull

We can see the following error in the logs:

2015-02-25 10:06:21,915 - INFO environment.py:322 -- Waiting for admin node to start up
2015-02-25 10:06:21,917 - INFO environment.py:324 -- Proceed with installation
2015-02-25 10:10:13,875 - INFO environment.py:300 -- Admin node login name: 'root' , password: 'r00tme'
2015-02-25 10:10:13,875 - INFO environment.py:416 -- Waiting while bootstrapping is in progress
2015-02-25 10:10:13,875 - INFO environment.py:419 -- Puppet timeout set in 6000.0
2015-02-25 11:05:24,833 - WARNING http.py:95 -- Authorization failure: Authentication required
2015-02-25 11:05:24,833 - INFO http.py:37 -- Initialize keystoneclient with url http://10.109.5.2:5000/v2.0
2015-02-25 11:05:24,983 - WARNING http.py:47 -- Cant establish connection to keystone with url http://10.109.5.2:5000/v2.0

Looks like keystone was not properly installed on the master node as well as other services in containers:
[mNotice: /Stage[main]/Docker/Exec[build docker containers]/returns: ERROR: postgres failed to start.
[mNotice: /Stage[main]/Docker/Exec[build docker containers]/returns: ERROR: keystone failed to start.

[Tatyanka (tatyana-leontovich)]

Guys, why this issue assigned to qa? You have failed deploy of master node(so looks like you need find the reason why, may be you miss some package) and fix it

[Bug Checker Bot (esikachev-l)]

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

version

expected result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

[Alexei Sheplyakov (asheplyakov)]

@Tatyana

> why this issue assigned to qa?

I guess the idea was to ask the qa team to recheck if the problem still happens with MOS 9.0.
Most likely it's not, since as of MOS 9.0 Fuel components (nailgun, astute) and related services (cobbler,
mcollective, etc) are deployed directly into the host system (as opposed to using containers).

P. S. Assigning this bug to Ceph team makes little sense (if any at all).