Unable to install ALLinONE Packstack on Centos 7 Queens release.

[pothireddyashok]

Infra: ESX host, 6.5 ESXI.
VM : 16 GB RAM , CPU=4 ,OS: Centos 7,

Files attached for reference.

Error:
apply is finished: 172.22.5.150_controller.pp [ / ]
Testing if puppet apply is finished: 172.22.5.150_controller.pp [ | ]
Testing if puppet apply is finished: 172.22.5.150_controller.pp [ \ ]
Testing if puppet apply is finished: 172.22.5.150_controller.pp [ - ]
Testing if puppet apply is finished: 172.22.5.150_controller.pp [ / ]
Testing if puppet apply is finished: 172.22.5.150_controller.pp [ | ]
Testing if puppet apply is finished: 172.22.5.150_controller.pp [ \ ]
Testing if puppet apply is finished: 172.22.5.150_controller.pp [ - ]
Testing if puppet apply is finished: 172.22.5.150_controller.pp [ / ]
Testing if puppet apply is finished: 172.22.5.150_controller.pp [ | ]

172.22.5.150_controller.pp: [ ERROR ]
Applying Puppet manifests [ ERROR ]

ERROR : Error appeared during Puppet run: 172.22.5.150_controller.pp
Error: Failed to apply catalog: Could not authenticate
You will find full trace in log /var/tmp/packstack/20180503-202117-mivlgT/manifests/172.22.5.150_controller.pp.log
Please check log file /var/tmp/packstack/20180503-202117-mivlgT/openstack-setup.log for more information
Additional information:
 * A new answerfile was created in: /root/packstack-answers-20180503-202119.txt
 * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components.
 * File /root/keystonerc_admin has been created on OpenStack client host 172.22.5.150. To use the command line tools you need to source the file.
 * To access the OpenStack Dashboard browse to http://172.22.5.150/dashboard .
Please, find your login credentials stored in the keystonerc_admin in your home directory.
 * Note temporary directory /var/tmp/packstack/582d5aa8469641ecbc1e8d67e3fd9512 on host 172.22.5.150 was not deleted for debugging purposes.

[Javier Peña (jpena-c)]

Thanks for your bug report. I see the authentication error happens right after restarting httpd, which is used by Keystone. Have you checked the logs under /var/log/httpd?

Also, which version of RDO are you testing? Queens, or trunk?

[pothireddyashok (ashok.pothireddy)]

Thanks for reply , we are using Queens .
Setup instructions from : https://www.rdoproject.org/install/packstack/

[root@SRV-OPENSTACK-ALLPACK httpd]# ll
total 132
-rw-r--r--. 1 root root 0 May 3 18:32 access_log
-rw-r--r--. 1 root root 0 May 3 18:32 aodh_wsgi_access.log
-rw-r--r--. 1 root root 0 May 3 18:32 aodh_wsgi_error.log
-rw-r--r--. 1 root root 0 May 3 18:32 default_error.log
-rw-r--r--. 1 root root 23762 May 4 00:23 error_log
-rw-r--r--. 1 root root 10282 May 3 20:26 gnocchi_wsgi_access.log
-rw-r--r--. 1 root root 0 May 3 18:32 gnocchi_wsgi_error.log
-rw-r--r--. 1 root root 5959 May 3 19:55 horizon_access.log
-rw-r--r--. 1 root root 1311 May 3 19:54 horizon_error.log
-rw-r--r--. 1 root root 58577 May 3 20:26 keystone_wsgi_admin_access.log
-rw-r--r--. 1 root root 0 May 3 18:32 keystone_wsgi_admin_error.log
-rw-r--r--. 1 root root 24023 May 4 00:31 keystone_wsgi_main_access.log
-rw-r--r--. 1 root root 0 May 3 18:32 keystone_wsgi_main_error.log
-rw-r--r--. 1 root root 0 May 3 18:32 placement_wsgi_access.log
-rw-r--r--. 1 root root 0 May 3 18:32 placement_wsgi_error.log
[root@SRV-OPENSTACK-ALLPACK httpd]#

Which file you need ?

[Javier Peña (jpena-c)]

Hi,

Looking at the logs, there is something I cannot understand. Your Packstack setup started at 20:21, however I can see activity in Keystone about 2 hours earlier, some of them related to the project domains. For example:

127.0.0.1 - - [03/May/2018:18:32:29 +0530] "GET /v3/domains HTTP/1.1" 200 172 "-" "python-keystoneclient"

That is a successful request to get all domains, the equivalent to '/usr/bin/openstack domain list --quiet --format csv'.

Also, I cannot find any authentication error in the keystone logs.

Did you run "packstack --allinone" twice? If so, that could explain the issue. The second time, Packstack would be trying to generate different passwords for all services, which did not match the existing passwords.

If you wanted to change something in the configuration, you have to modify the answers file (usually under /root/packstack-answers-xxx.txt), and re-run with "packstack --answer-file=/root/packstack-answers-xxx.txt".

[pothireddyashok (ashok.pothireddy)]

Yes we been trying multiple times, after our first attempt failed with answer file .
If one attempt fails , cant we re-run without any answer file ?

[Javier Peña (jpena-c)]

No, it is not possible to re-run without specifying an answer file. Doing so will change the randomly generated passwords for some services, and that will create all sort of problems.

[pothireddyashok (ashok.pothireddy)]

Thanks , Then I guess we messed it up. We will create fresh VM and start again.
Do you have any documentation for workflow or to explain behind the scene of packstack.

[Javier Peña (jpena-c)]

There is not a lot of documentation about the Packstack internals, I wrote a blog post some time ago at https://jpenatech.wordpress.com/2014/09/29/writing-packstack-plugins/ (most of it is still valid).

I'm closing the bug as invalid, feel free to open a new one if you find further issues in the next installation.

[anwar sayyed (kayyumanwar)]

Thanks for your Help.

[Francis Santana (fsantana18)]

Hi Reddy i this issue now resolved, I have the same issue but also tried using the answer file but issue still persists, any resolution.

Thanks