Bug 1371280 - Openstack 9 deployment with packstack complete but fail when we try to login [NEEDINFO]
Summary: Openstack 9 deployment with packstack complete but fail when we try to login
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack
Version: 9.0 (Mitaka)
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 10.0 (Newton)
Assignee: Ivan Chavero
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-29 19:19 UTC by Alessandro Silva
Modified: 2020-12-28 12:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-11 18:25:51 UTC
Target Upstream Version:
ichavero: needinfo? (alsilva)


Attachments (Terms of Use)
Packstack file (deleted)
2016-08-29 19:19 UTC, Alessandro Silva
no flags Details

Description Alessandro Silva 2016-08-29 19:19:05 UTC
Description of problem:

After to generate an answer file and deploy Openstack 9 using packstack,the deployment complete sucessfuly, but I'm not able to login with admin user and password defined in the answer file

Version-Release number of selected component (if applicable):

Red Hat Openstack Platform 9


How reproducible:

1. Generate packstack file

   # packstack --gen-answer-file=packstack-new

2. Edit packstack file and enable some service

   - TROVE
   - LBAAS
   - VPNASS
   - SAHARA
   - MANILLA
   - HEAT

   
3. Run packstack

   # packstack --answer-file=packstack-new


Actual results:


**** Installation completed successfully ******

Additional information:
 * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components.
 * NOTE : A selfsigned CA certificate was generated to be used for ssl, you should still change it do subordinate CA cert. In any case please save the contents of /root/packstackca/.
 * File /root/keystonerc_admin has been created on OpenStack client host 192.168.124.28. To use the command line tools you need to source the file.
 * NOTE : A certificate was generated to be used for ssl, You should change the ssl certificate configured in /etc/httpd/conf.d/ssl.conf on 192.168.124.28 to use a CA signed cert.
 * To access the OpenStack Dashboard browse to https://192.168.124.28/dashboard .
Please, find your login credentials stored in the keystonerc_admin in your home directory.
 * The installation log file is available at: /var/tmp/packstack/20160829-140502-jVIsqu/openstack-setup.log
 * The generated manifests are available at: /var/tmp/packstack/20160829-140502-jVIsqu/manifests


So, I'm not able to login in the webUI using ADMIN credentials defined in the packstack file.


However, I'm able to use ADMIN credential by command OS command line:

[root@openstack ~]# source keystonerc_admin 
[root@openstack ~(keystone_admin)]# cat keystonerc_admin 
unset OS_SERVICE_TOKEN
export OS_USERNAME=admin
export OS_PASSWORD=redhat
export OS_AUTH_URL=http://192.168.124.28:5000/v2.0
export PS1='[\u@\h \W(keystone_admin)]\$ '

export OS_TENANT_NAME=admin
export OS_REGION_NAME=RegionOne
[root@openstack ~(keystone_admin)]# nova list
+----+------+--------+------------+-------------+----------+
| ID | Name | Status | Task State | Power State | Networks |
+----+------+--------+------------+-------------+----------+
+----+------+--------+------------+-------------+----------+


Expected results:

1. Openstack installed successfully using the packstack file attached 
2. Able to login in the webUI with the credentials defined in the packstack file.

Comment 5 Alessandro Silva 2016-09-19 12:20:41 UTC
I'm not able to login in the webUI using the credentials provided by  keystonerc_admin. However, I'm able to use command line after source this file.
The problem is with Horizon.

Comment 6 Ivan Chavero 2016-10-01 01:42:00 UTC
can't reproduce this problem, can you provide the horizon log file?

Comment 7 Ivan Chavero 2016-10-11 16:37:03 UTC
Just tested this again and could not reproduce, does the problem persist?

Comment 8 Ivan Chavero 2016-10-11 18:25:51 UTC
i'm closing the bug, feel free to reopen it if the problem persists.


Note You need to log in before you can comment on or make changes to this bug.