Thanks Gabriele,
I've found the error log, which is in undercloud vm and not on the physical
machine.
The error is:
2019-01-30 16:56:22 | CommunicationError: Error communicating with
[Errno 5]
Input/output error
but I an also see:
2019-01-30 16:56:22 | Image "overcloud-full-vmlinuz" was uploaded.
which seems at least strange.
At the end of the log I see:
2019-01-30 16:56:22 |
+--------------------------------------+------------------------+-------------+---------+--------+
2019-01-30 16:56:22 | | ID | Name |
Disk Format | Size | Status |
2019-01-30 16:56:22 |
+--------------------------------------+------------------------+-------------+---------+--------+
2019-01-30 16:56:22 | | 0db17f9b-9732-4a02-bed9-ead9c453cfe1 | overcloud-full-vmlinuz |
aki | 6639808 | active |
2019-01-30 16:56:22 |
+--------------------------------------+------------------------+-------------+---------+--------+
2019-01-30 16:56:22 | Image "overcloud-full-initrd" was uploaded.
2019-01-30 16:56:22 |
+--------------------------------------+-----------------------+-------------+----------+--------+
2019-01-30 16:56:22 | | ID | Name |
Disk Format | Size | Status |
2019-01-30 16:56:22 |
+--------------------------------------+-----------------------+-------------+----------+--------+
2019-01-30 16:56:22 | | 8af30460-4fcf-43e6-a99e-961c92f75a6e | overcloud-full-initrd |
ari | 51767348 | active |
2019-01-30 16:56:22 |
+--------------------------------------+-----------------------+-------------+----------+--------+
How can I investigate why it failed to upload ?
He is actually runnin all on a physical machine.
Thx
Pierluigi
On Thursday 31 January 2019 09:26:59 Gabriele Cerami wrote:
On 30 Jan, Pigi wrote:
Hi
> Hi all,
> I'm trying to setup an environment for test using quickstart.sh
>
> On my previous attempt I was on vmware and had quite a lot of trouble, then I deided
to go with physical servers.
> Everything seemed to be fine until I hit an error:
>
> TASK [overcloud-prep-images : Prepare the overcloud images for deploy]
*******************************************************************************************************************************************
> task path:
/root/.quickstart/usr/local/share/ansible/roles/overcloud-prep-images/tasks/overcloud-prep-images.yml:2
> Wednesday 30 January 2019 17:55:26 +0100 (0:00:08.814) 3:19:01.327 *****
> fatal: [undercloud]: FAILED! => {
> "changed": true,
> "cmd": "set -o pipefail &&
/home/stack/overcloud-prep-images.sh 2>&1 | awk '{ print
strftime(\"%Y-%m-%d %H:%M:%S |\"), $0; fflush(); }' >
/home/stack/overcloud_prep_images.log",
1) if you look closely at the error message, the complete command that
fails is shown, and most of the commands in quickstart log to the home
directory of the user. In this case your specific error is in
/home/stack/overcloud_prep_images.log
In /home/stack you'll find also all the other output for the other
commands, past and future.
2) This answer is not simple. The default playbook launched by
quickstart is quickstart-extras.yml, which in turn includes a list of
playbooks run in sequence. We made effort to ensure that the playbooks
can be called independently, but you'll need to pass the proper
variables to each of them, and this requires some knowledge on what the
playbooks need.
Basically you need the expansion of this line
http://git.openstack.org/cgit/openstack/tripleo-quickstart/tree/quickstar...
What I would suggest is to modify quickstart.sh and add a set -x at the
start, then add a echo at the start of that line, so you'll do a dry run,
but it will show what is launched, then you can replace the call to
quickstart-extras playbook to one on the list, in your case you can use
quickstart-extras-overcloud-prep.yml, which is the one that failed
for you.
We are working on making this interface frendlier.