Hello,
I was able the resolve this issue by tracing back through the installation logs and
ansible scripts. I created a PR that was subsequently closed by Gerrit as I am unfamiliar
with the code submission process with OpenStack. I’ll work through that and get this PR
submitted properly.
See:
On Jul 15, 2016, at 4:44 PM, Brandon Gaisford
<bgaisford(a)punagroup.com> wrote:
Digging deeper…searched maui: /root/quickstart.sh
Toward the end:
##################################
Virtual Environment Setup Complete
##################################
Access the undercloud by:
ssh -F $OPT_WORKDIR/ssh.config.ansible undercloud
There are scripts in the home directory to continue the deploy:
overcloud-deploy.sh will deploy the overcloud
overcloud-deploy-post.sh will do any post-deploy configuration
overcloud-validate.sh will run post-deploy validation
Alternatively, you can ignore these scripts and follow the upstream docs,
starting from the overcloud deploy section:
http://ow.ly/1Vc1301iBlb
##################################
Virtual Environment Setup Complete
##################################
Note: In this case, $OPT_WORKDIR = /root/.quickstart on the maui box
[root@maui ~]# cd .quickstart/
[root@maui .quickstart]# ssh -F ssh.config.ansible undercloud
[stack@undercloud ~]$ ll
total 1534224
-rw-rw-r--. 1 1001 1001 10804 Jul 15 23:44 instackenv.json
-rw-r--r--. 1 root root 343696519 Jul 14 17:25 ironic-python-agent.initramfs
-rwxr-xr-x. 1 root root 5158704 Jul 14 17:25 ironic-python-agent.kernel
-rw-r--r--. 1 root root 36456036 Jul 14 17:25 overcloud-full.initrd
-rw-r--r--. 1 root root 1179742720 Jul 14 17:25 overcloud-full.qcow2
-rwxr-xr-x. 1 root root 5158704 Jul 14 17:26 overcloud-full.vmlinuz
-rw-------. 1 stack stack 6559 Jul 15 23:49 undercloud.conf
-rw-rw-r--. 1 stack stack 785510 Jul 16 00:14 undercloud_install.log
-rwxr-xr-x. 1 stack stack 83 Jul 15 23:49 undercloud-install.sh
-rw-rw-r--. 1 stack stack 1579 Jul 15 23:49 undercloud-passwords.conf
-rwxr-xr-x. 1 stack stack 2865 Jul 15 23:49 undercloud-post-install.sh
Seems to be a disconnect here between the “setup complete” instructions and reality. I’m
wondering if the installation failure caused the discrepancy.
Thanks in advance for your eyes and any advice.
Brandon
> On Jul 15, 2016, at 2:45 PM, Brandon Gaisford <bgaisford(a)punagroup.com> wrote:
>
> Hello,
>
> Just attempted my first RDO TripleO installation - thank you in advance for all your
hard work to make this a simple process!!
>
> Environment:
>
> Server: blade0 is the target host, CentOS7 32GB RAM, 1TB HDD, SSH trust with server:
maui
> Server: maui is the ansible server executing the TripleO quickstart.sh script
>
> Results:
>
> PLAY RECAP *********************************************************************
>
blade0.punagroup.com : ok=77 changed=49 unreachable=0 failed=0
> localhost : ok=15 changed=7 unreachable=0 failed=0
> undercloud : ok=5 changed=3 unreachable=0 failed=1
>
> Please see attached log. It looks as if the setup went pretty well, but given the
playlist recap and since there was’t any info at the end of the run explaining how to
connect to the new system, I have my suspicions.
>
> Brandon
>
> <RDO-TripleO-install.log>
>
>
>
>
>
> _______________________________________________
> rdo-list mailing list
> rdo-list(a)redhat.com
>
https://www.redhat.com/mailman/listinfo/rdo-list
>
> To unsubscribe: rdo-list-unsubscribe(a)redhat.com
_______________________________________________
rdo-list mailing list
rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com