Bug 1248388

Summary: no overcloudrc file after deployment via UI
Product: Red Hat OpenStack Reporter: Ola Pavlenko <opavlenk>
Component: rhosp-directorAssignee: Brad P. Crochet <brad>
Status: CLOSED ERRATA QA Contact: Ola Pavlenko <opavlenk>
Severity: high Docs Contact:
Priority: unspecified    
Version: DirectorCC: brad, calfonso, kaihua.chen, mburns, nbarcet, ohochman, rhel-osp-director-maint, sputhenp
Target Milestone: asyncKeywords: ZStream
Target Release: Director   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-tuskar-ui-0.3.0-15.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-13 20:04:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ola Pavlenko 2015-07-30 08:09:06 UTC
Description of problem:
deployment via UI doesn't create overcloudrc file

Version-Release number of selected component (if applicable):
openstack-tuskar-ui-extras-0.0.4-1.el7ost.noarch
openstack-tuskar-ui-0.3.0-13.el7ost.noarch
rhos-release-0.65-1.noarch

How reproducible:
100%

Steps to Reproduce:
1.Use Undercloud UI to deploy openstack
2.in command line source overcloudrc file
3. access controller node

Actual results:
no overcloudrc file in /home/stack dir

Expected results:
overcloudrc exists

Additional info:

Comment 4 Omri Hochman 2015-08-13 18:56:33 UTC
Verified : openstack-tuskar-ui-0.3.0-15.el7ost .

After deploying using the UI and initializing the overcloud - I could see in the overview tab the overcloudrc information , as well I cloud click the 'Download' button and get the file.  after source the file as stack on the instack machine It seems that the overcloudrc file is valid and I could communicate correctly and use the overcloud cli.

Comment 6 errata-xmlrpc 2015-08-13 20:04:02 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2015:1624