Mailing List Archive: [tripleo] [tripleo-quickstart] quickstart.sh failing

[tripleo] [tripleo-quickstart] quickstart.sh failing

Jun 20, 2018, 5:32 PM

Post #1 of 4 (465 views)

I hoped that I could use quickstart.sh to set up Tripleo without much
thinking. The Ansible playbook generates undercloud, compute and control
images and much more on the VIRTHOST but ultimately fails with:

TASK [undercloud-deploy : Write containers-prepare-parameter.yaml]
**************************************************************************
task path:
/home/stack/.quickstart/usr/local/share/ansible/roles/undercloud-deploy/tasks/create-scripts.yml:96
Wednesday 20 June 2018 18:31:07 +0900 (0:00:07.221)       1:14:05.859
********
fatal: [undercloud]: FAILED! => {"changed": false, "failed": true,
"msg": "AnsibleUndefinedVariable: 'container_build_id' is undefined"}

What puzzles me (I am far from being an Ansible expert): If I interpret
/_quickstart.log/ correctly, this variable is set about half-way through
the process:

TASK [extras-common : set container_build_id from docker_image_tag]
*************************************************************************
task path:
/home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:19
Wednesday 20 June 2018 17:23:13 +0900 (0:00:00.212)       0:06:12.229
********
ok: [jupiter] => {*"ansible_facts": {"container_build_id":
"current-tripleo-rdo"},* "changed": false, "failed": false}

Later plays also set it conditionally, but the conditions are never met.
Some derive it from a variable named /get_build_command/, which I can't
find anywhere (I did do a http://codesearch.openstack.org):

TASK [extras-common : set container_build_id from get_build_command]
************************************************************************
task path:
/home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:6
Wednesday 20 June 2018 18:16:45 +0900 (0:00:00.323)       0:59:44.741
********
skipping: [jupiter] => {"changed": false, "skip_reason": "Conditional
result was False", "skipped": true}

others base it on a Docker container tag:

TASK [extras-common : set container_build_id from docker_image_tag]
*************************************************************************
task path:
/home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:19
Wednesday 20 June 2018 18:16:46 +0900 (0:00:00.128)       0:59:44.996
********
skipping: [jupiter] => {"changed": false, "skip_reason": "Conditional
result was False", "skipped": true}

Any pointers how to fix this?

My VIRTHOST is a HP Z420 workstation named /jupiter/, 4 core Xeon, 32G
memory, 150G disk space running freshly installed Centos 7.5. I run the
quickstart script on a VM, equally with Centos 7.5. I followed the
instructions at
https://docs.openstack.org/tripleo-quickstart/latest/readme.html#tripleo-quickstart:

$ ssh-keygen; ssh-copy-id root@jupiter; ssh-copy-id stack@jupiter
$
curl-Ohttps://raw.githubusercontent.com/openstack/tripleo-quickstart/master/quickstart.sh
$ bashquickstart.sh--install-deps
$ bash quickstart.sh jupiter

Bernd Bausch

Re: [tripleo] [tripleo-quickstart] quickstart.sh failing [ In reply to ]

majopela at redhat

Jun 21, 2018, 12:43 AM

Post #2 of 4 (464 views)

Permalink

I'm also hitting that issue currently too

you can workaround with

-e docker_registry_namespace_used=tripleomaster -e
container_build_id=current-tripleo

on the quickstart command line while this is fixed (please note that's only
for tripleo master).

I see in the quickstart logs that those variables are detected as facts,
but then ansible does
not find them on those tasks.

Note: I'm just providing a workaround that I used to keep moving, but I'm
not actively working
on fixing the quickstart issue because I don't know how to fix it at this
moment.

On Thu, Jun 21, 2018 at 2:44 AM Bernd Bausch <berndbausch@gmail.com> wrote:

> I hoped that I could use quickstart.sh to set up Tripleo without much
> thinking. The Ansible playbook generates undercloud, compute and control
> images and much more on the VIRTHOST but ultimately fails with:
>
> TASK [undercloud-deploy : Write containers-prepare-parameter.yaml]
> **************************************************************************
> task path:
> /home/stack/.quickstart/usr/local/share/ansible/roles/undercloud-deploy/tasks/create-scripts.yml:96
> Wednesday 20 June 2018 18:31:07 +0900 (0:00:07.221) 1:14:05.859
> ********
> fatal: [undercloud]: FAILED! => {"changed": false, "failed": true, "msg":
> "AnsibleUndefinedVariable: 'container_build_id' is undefined"}
> What puzzles me (I am far from being an Ansible expert): If I interpret
> *_quickstart.log* correctly, this variable is set about half-way through
> the process:
>
> TASK [extras-common : set container_build_id from docker_image_tag]
> *************************************************************************
> task path:
> /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:19
> Wednesday 20 June 2018 17:23:13 +0900 (0:00:00.212) 0:06:12.229
> ********
> ok: [jupiter] => {*"ansible_facts": {"container_build_id":
> "current-tripleo-rdo"},* "changed": false, "failed": false}
>
> Later plays also set it conditionally, but the conditions are never met.
> Some derive it from a variable named *get_build_command*, which I can't
> find anywhere (I did do a http://codesearch.openstack.org):
>
> TASK [extras-common : set container_build_id from get_build_command]
> ************************************************************************
> task path:
> /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:6
> Wednesday 20 June 2018 18:16:45 +0900 (0:00:00.323) 0:59:44.741
> ********
> skipping: [jupiter] => {"changed": false, "skip_reason": "Conditional
> result was False", "skipped": true}
>
> others base it on a Docker container tag:
>
> TASK [extras-common : set container_build_id from docker_image_tag]
> *************************************************************************
> task path:
> /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:19
> Wednesday 20 June 2018 18:16:46 +0900 (0:00:00.128) 0:59:44.996
> ********
> skipping: [jupiter] => {"changed": false, "skip_reason": "Conditional
> result was False", "skipped": true}
>
> Any pointers how to fix this?
>
> My VIRTHOST is a HP Z420 workstation named *jupiter*, 4 core Xeon, 32G
> memory, 150G disk space running freshly installed Centos 7.5. I run the
> quickstart script on a VM, equally with Centos 7.5. I followed the
> instructions at
> https://docs.openstack.org/tripleo-quickstart/latest/readme.html#tripleo-quickstart
> :
>
> $ ssh-keygen; ssh-copy-id root@jupiter; ssh-copy-id stack@jupiter
> $ curl -O https://raw.githubusercontent.com/openstack/tripleo-quickstart/
> master/quickstart.sh
> $ bash quickstart.sh --install-deps
> $ bash quickstart.sh jupiter
>
> Bernd Bausch
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>

Re: [tripleo] [tripleo-quickstart] quickstart.sh failing [ In reply to ]

berndbausch at gmail

Jun 22, 2018, 1:47 AM

Post #3 of 4 (460 views)

Permalink

Thanks Miguel! When I set these variables, the quickstart script
completes successfully.

Bernd Bausch

On 6/21/2018 4:43 PM, Miguel Angel Ajo Pelayo wrote:
> I'm also hitting that issue currently too
>
> you can workaround with
>
> -e docker_registry_namespace_used=tripleomaster -e
> container_build_id=current-tripleo
>
> on the quickstart command line while this is fixed (please note that's
> only for tripleo master).
>
>
> I see in the quickstart logs that those variables are detected as
> facts, but then ansible does
> not find them on those tasks.
>
> Note: I'm just providing a workaround that I used to keep moving, but
> I'm not actively working
> on fixing the quickstart issue because I don't know how to fix it at
> this moment.
>
>
>
>
> On Thu, Jun 21, 2018 at 2:44 AM Bernd Bausch <berndbausch@gmail.com
> <mailto:berndbausch@gmail.com>> wrote:
>
> I hoped that I could use quickstart.sh to set up Tripleo without
> much thinking. The Ansible playbook generates undercloud, compute
> and control images and much more on the VIRTHOST but ultimately
> fails with:
>
> TASK [undercloud-deploy : Write containers-prepare-parameter.yaml]
> **************************************************************************
> task path:
> /home/stack/.quickstart/usr/local/share/ansible/roles/undercloud-deploy/tasks/create-scripts.yml:96
> Wednesday 20 June 2018 18:31:07 +0900 (0:00:07.221)
> 1:14:05.859 ********
> fatal: [undercloud]: FAILED! => {"changed": false, "failed": true,
> "msg": "AnsibleUndefinedVariable: 'container_build_id' is undefined"}
>
> What puzzles me (I am far from being an Ansible expert): If I
> interpret /_quickstart.log/ correctly, this variable is set about
> half-way through the process:
>
> TASK [extras-common : set container_build_id from
> docker_image_tag]
> *************************************************************************
> task path:
> /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:19
> Wednesday 20 June 2018 17:23:13 +0900 (0:00:00.212)
> 0:06:12.229 ********
> ok: [jupiter] => {*"ansible_facts": {"container_build_id":
> "current-tripleo-rdo"},* "changed": false, "failed": false}
>
> Later plays also set it conditionally, but the conditions are
> never met. Some derive it from a variable named
> /get_build_command/, which I can't find anywhere (I did do a
> http://codesearch.openstack.org):
>
> TASK [extras-common : set container_build_id from
> get_build_command]
> ************************************************************************
> task path:
> /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:6
> Wednesday 20 June 2018 18:16:45 +0900 (0:00:00.323)
> 0:59:44.741 ********
> skipping: [jupiter] => {"changed": false, "skip_reason":
> "Conditional result was False", "skipped": true}
>
> others base it on a Docker container tag:
>
> TASK [extras-common : set container_build_id from
> docker_image_tag]
> *************************************************************************
> task path:
> /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:19
> Wednesday 20 June 2018 18:16:46 +0900 (0:00:00.128)
> 0:59:44.996 ********
> skipping: [jupiter] => {"changed": false, "skip_reason":
> "Conditional result was False", "skipped": true}
>
> Any pointers how to fix this?
>
> My VIRTHOST is a HP Z420 workstation named /jupiter/, 4 core Xeon,
> 32G memory, 150G disk space running freshly installed Centos 7.5.
> I run the quickstart script on a VM, equally with Centos 7.5. I
> followed the instructions at
> https://docs.openstack.org/tripleo-quickstart/latest/readme.html#tripleo-quickstart:
>
> $ ssh-keygen; ssh-copy-id root@jupiter; ssh-copy-id stack@jupiter
> $
> curl-Ohttps://raw.githubusercontent.com/openstack/tripleo-quickstart/master/quickstart.sh
> $ bashquickstart.sh--install-deps
> $ bash quickstart.sh jupiter
>
> Bernd Bausch
>
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> <mailto:openstack@lists.openstack.org>
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>

Re: [tripleo] [tripleo-quickstart] quickstart.sh failing [ In reply to ]

majopela at redhat

Jun 25, 2018, 2:21 AM

Post #4 of 4 (459 views)

Permalink

I got that working too, but then:

1) my undercloud didn't have any hosts when I did openstack server list
over stackrc
2) I had no overcloud-deploy.sh of any kind

Folks I need help with this, I'm blocked.

On Fri, Jun 22, 2018 at 10:48 AM Bernd Bausch <berndbausch@gmail.com> wrote:

> Thanks Miguel! When I set these variables, the quickstart script completes
> successfully.
>
> Bernd Bausch
> On 6/21/2018 4:43 PM, Miguel Angel Ajo Pelayo wrote:
>
> I'm also hitting that issue currently too
>
> you can workaround with
>
> -e docker_registry_namespace_used=tripleomaster -e
> container_build_id=current-tripleo
>
> on the quickstart command line while this is fixed (please note that's
> only for tripleo master).
>
>
> I see in the quickstart logs that those variables are detected as facts,
> but then ansible does
> not find them on those tasks.
>
> Note: I'm just providing a workaround that I used to keep moving, but I'm
> not actively working
> on fixing the quickstart issue because I don't know how to fix it at this
> moment.
>
>
>
>
> On Thu, Jun 21, 2018 at 2:44 AM Bernd Bausch <berndbausch@gmail.com>
> wrote:
>
>> I hoped that I could use quickstart.sh to set up Tripleo without much
>> thinking. The Ansible playbook generates undercloud, compute and control
>> images and much more on the VIRTHOST but ultimately fails with:
>>
>> TASK [undercloud-deploy : Write containers-prepare-parameter.yaml]
>> **************************************************************************
>> task path:
>> /home/stack/.quickstart/usr/local/share/ansible/roles/undercloud-deploy/tasks/create-scripts.yml:96
>> Wednesday 20 June 2018 18:31:07 +0900 (0:00:07.221) 1:14:05.859
>> ********
>> fatal: [undercloud]: FAILED! => {"changed": false, "failed": true, "msg":
>> "AnsibleUndefinedVariable: 'container_build_id' is undefined"}
>> What puzzles me (I am far from being an Ansible expert): If I interpret
>> *_quickstart.log* correctly, this variable is set about half-way through
>> the process:
>>
>> TASK [extras-common : set container_build_id from docker_image_tag]
>> *************************************************************************
>> task path:
>> /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:19
>> Wednesday 20 June 2018 17:23:13 +0900 (0:00:00.212) 0:06:12.229
>> ********
>> ok: [jupiter] => {*"ansible_facts": {"container_build_id":
>> "current-tripleo-rdo"},* "changed": false, "failed": false}
>>
>> Later plays also set it conditionally, but the conditions are never met.
>> Some derive it from a variable named *get_build_command*, which I can't
>> find anywhere (I did do a http://codesearch.openstack.org):
>>
>> TASK [extras-common : set container_build_id from get_build_command]
>> ************************************************************************
>> task path:
>> /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:6
>> Wednesday 20 June 2018 18:16:45 +0900 (0:00:00.323) 0:59:44.741
>> ********
>> skipping: [jupiter] => {"changed": false, "skip_reason": "Conditional
>> result was False", "skipped": true}
>>
>> others base it on a Docker container tag:
>>
>> TASK [extras-common : set container_build_id from docker_image_tag]
>> *************************************************************************
>> task path:
>> /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:19
>> Wednesday 20 June 2018 18:16:46 +0900 (0:00:00.128) 0:59:44.996
>> ********
>> skipping: [jupiter] => {"changed": false, "skip_reason": "Conditional
>> result was False", "skipped": true}
>>
>> Any pointers how to fix this?
>>
>> My VIRTHOST is a HP Z420 workstation named *jupiter*, 4 core Xeon, 32G
>> memory, 150G disk space running freshly installed Centos 7.5. I run the
>> quickstart script on a VM, equally with Centos 7.5. I followed the
>> instructions at
>> https://docs.openstack.org/tripleo-quickstart/latest/readme.html#tripleo-quickstart
>> :
>>
>> $ ssh-keygen; ssh-copy-id root@jupiter; ssh-copy-id stack@jupiter
>> $ curl -O https://raw.githubusercontent.com/openstack/tripleo-quickstart/
>> master/quickstart.sh
>> $ bash quickstart.sh --install-deps
>> $ bash quickstart.sh jupiter
>>
>> Bernd Bausch
>> _______________________________________________
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>
>

Mailing List Archive

Attached Files:

Attached Files: