> I am new to containers, can I somehow transfer these images between, as I understand, it might help?
The image will be downloaded automatically with the installation, you don't need to do it manually.
The problem seems to be that the container failed to start, not the errors in the images themselves.
You may need to check the configuration of undercloud.conf and proxy settings (if they exist).
From: Ruslanas Gžibovskis <ruslanas@lpic.lt>
Sent: 2020年4月29日 15:48
To: Alex Schultz <aschultz@redhat.com>
Cc: Openstack-discuss <openstack-discuss@lists.openstack.org>; kent.martin@ericsson.com
Subject: Re: [TripleO][train][rdo] installation of undercloud fails during Run container-puppet tasks step1
On the other installation I have, I see a bit more images:
I am new to containers, can I somehow transfer these images between, as I understand, it might help?
On Wed, 29 Apr 2020 at 09:45, Ruslanas Gžibovskis <ruslanas@lpic.lt> wrote:
I just now realized, that I have seen in some log, messages, missing some puppet-dependencies... Cannot find log again...
On Wed, 29 Apr 2020 at 09:39, Ruslanas Gžibovskis <ruslanas@lpic.lt> wrote:
podman ps -a = clean, no containers at all.
I have a watch -d "sudo podman ps -a ; sudo podman images -a ; sudo df -h"
paunch.log is empty. (I did several reinstallations).
Later I saw connectionpool retrying, but I have not seen " tripleo_common.image.image_uploader" with same.
On Tue, 28 Apr 2020 at 20:10, Alex Schultz <aschultz@redhat.com> wrote:
On Tue, Apr 28, 2020 at 11:57 AM Ruslanas Gžibovskis <ruslanas@lpic.lt> wrote:
>
> Hi all,
>
> I am running a fresh install of rdo train, on centos7
> I almost a week I am facing error at this step:
> TASK [Run container-puppet tasks (generate config) during step 1]
>
> So I have ansible.log attached, I cannot find anything, where it is failing.
> According to some understanding in ansible, it fails if it finds stderr output.
> I cannot find error/fail or smth, I see Notices and Warnings, but I believe it is not stderr?
>
> I see containers running and removed after some time.
> (as it should be I think)...
>
> Could you help me, where to dig?
>
2020-04-27 22:27:46,147 p=132230 u=root | TASK [Start containers for
step 1 using paunch]
*****************************************************************************************************************************
2020-04-27 22:27:46,148 p=132230 u=root | Monday 27 April 2020
22:27:46 +0200 (0:00:00.137) 0:04:44.326 **********?
2020-04-27 22:27:46,816 p=132230 u=root | ok: [remote-u]
2020-04-27 22:27:46,914 p=132230 u=root | TASK [Debug output for
task: Start containers for step 1]
*******************************************************************************************************************
2020-04-27 22:27:46,915 p=132230 u=root | Monday 27 April 2020
22:27:46 +0200 (0:00:00.767) 0:04:45.093 **********?
2020-04-27 22:27:46,977 p=132230 u=root | fatal: [remote-u]: FAILED! => {
"failed_when_result": true,?
"outputs.stdout_lines | default([]) | union(outputs.stderr_lines |
default([]))": []
Check /var/log/paunch.log. It probably has additional information as
to why the containers didn't start. You might also check the output
of 'sudo podman ps -a' to see if any containers exited with errors.
> --
> Ruslanas Gžibovskis
> +370 6030 7030
--
Ruslanas Gžibovskis
+370 6030 7030
--
Ruslanas Gžibovskis
+370 6030 7030
--
Ruslanas Gžibovskis
+370 6030 7030