[TripleO][train][rdo] installation of undercloud fails during Run container-puppet tasks step1

Ruslanas Gžibovskis ruslanas at lpic.lt
Sat May 2 11:23:41 UTC 2020


Hi all,

After executing: [stack at remote-u undercloud-ansible-CxDDOO]$ sudo
ansible-playbook-2 -vvvv -i inventory.yaml deploy_steps_playbook.yaml

not sure, who has no attribute:
  AttributeError: 'module' object has no attribute 'load_config'\n"



TASK [Start containers for step 1 using paunch]
*****************************************************************************************************************************
task path:
/home/stack/builddir/a/undercloud-ansible-CxDDOO/common_deploy_steps_tasks.yaml:257
Saturday 02 May 2020  13:11:01 +0200 (0:00:00.165)       0:04:57.422
**********
Using module file /usr/share/ansible/plugins/modules/paunch.py
Pipelining is enabled.
<10.120.129.222> ESTABLISH LOCAL CONNECTION FOR USER: root
<10.120.129.222> EXEC /bin/sh -c 'TRIPLEO_MINOR_UPDATE=False
/usr/bin/python2 && sleep 0'
ok: [remote-u] => {
    "changed": false,
    "failed_when_result": false,
    "module_stderr": "Traceback (most recent call last):\n  File
\"<stdin>\", line 114, in <module>\n  File \"<stdin>\", line 106, in
_ansiballz_main\n  File \"<stdin>\", line 49, in invoke_module\n  File
\"/tmp/ansible_paunch_payload_8IPdGs/__main__.py\", line 250, in <module>\n
 File \"/tmp/ansible_paunch_payload_8IPdGs/__main__.py\", line 246, in
main\n  File \"/tmp/ansible_paunch_payload_8IPdGs/__main__.py\", line 172,
in __init__\nAttributeError: 'module' object has no attribute
'load_config'\n",
    "module_stdout": "",
    "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error",
    "rc": 1
}

TASK [Debug output for task: Start containers for step 1]
*******************************************************************************************************************
task path:
/home/stack/builddir/a/undercloud-ansible-CxDDOO/common_deploy_steps_tasks.yaml:275
Saturday 02 May 2020  13:11:02 +0200 (0:00:00.901)       0:04:58.323
**********
fatal: [remote-u]: FAILED! => {
    "failed_when_result": true,
    "outputs.stdout_lines | default([]) | union(outputs.stderr_lines |
default([]))": []
}

NO MORE HOSTS LEFT
**********************************************************************************************************************************************************

PLAY RECAP
******************************************************************************************************************************************************************
remote-u                   : ok=242  changed=78   unreachable=0    failed=1
   skipped=94   rescued=0    ignored=2

On Sat, 2 May 2020 at 00:32, Ruslanas Gžibovskis <ruslanas at lpic.lt> wrote:

> Hi all,
>
> it was my error, that paunch did not launch containers when executed
> paunch manually.
> I have fixed log path to containers dir, and it worked, reexecuted
> undercloud deploy again with --force-stack-update
>
> and it failed again, same step, and did not exec paunch still.
>
>
>

-- 
Ruslanas Gžibovskis
+370 6030 7030
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200502/e136d428/attachment-0001.html>


More information about the openstack-discuss mailing list