Bug 1647001
| Summary: | Undercloud installation fails looking for non existing containers | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Raoul Scarazzini <rscarazz> |
| Component: | python-tripleoclient | Assignee: | RHOS Maint <rhos-maint> |
| Status: | CLOSED DUPLICATE | QA Contact: | Gurenko Alex <agurenko> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 14.0 (Rocky) | CC: | cjeanner, hbrock, jslagle, mburns, therve |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-08 10:24:20 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Hello Raoul, I'm not 100% sure this is the real issue - there are some "useless" logs due to paunch, but the fact it doesn't find some containers isn't critical. The "real" issue in your case seems to be: 2018-11-05 13:45:34.771 17169 WARNING tripleoclient.v1.tripleo_deploy.Deploy [ ] "2018-11-05 13:43:44,095 ERROR: 10577 -- Failed running docker-puppet.py for ironic", I'm trying to find the real root cause. Regarding the "Error" you find in the logs, it's related to this LP: https://bugs.launchpad.net/tripleo/+bug/1801939 Cheers, C. I would point to those failures in puppet: Nov 5 13:43:41 undercloud journal: Error: /Stage[main]/Ironic::Pxe/Ironic::Pxe::Tftpboot_file[pxelinux.0]/File[/var/lib/ironic/tftpboot/pxelinux.0]: Could not evaluate: Could not retrieve information from environment production source(s) file:/usr/share/syslinux/pxelinux.0 Nov 5 13:43:41 undercloud journal: Error: /Stage[main]/Ironic::Pxe/Ironic::Pxe::Tftpboot_file[chain.c32]/File[/var/lib/ironic/tftpboot/chain.c32]: Could not evaluate: Could not retrieve information from environment production source(s) file:/usr/share/syslinux/chain.c32 Source: both undercloud install log and host "messages", after some filtering: grep -i error messages | grep -v "No such container" | grep -v "does not exist" They are more likely the root cause. Maybe someone else can confirm? *** This bug has been marked as a duplicate of bug 1646584 *** |
Description of problem: The undercloud installation is failing with a lot of errors related to "No such container": 2018-11-05 13:45:34 | "2018-11-05 13:43:11,215 DEBUG: 10577 -- Error: No such container: docker-puppet-mysql", 2018-11-05 13:45:34 | "2018-11-05 13:43:11,215 DEBUG: 10575 -- Error: No such container: docker-puppet-nova_placement", 2018-11-05 13:45:34 | "2018-11-05 13:43:11,215 DEBUG: 10576 -- Error: No such container: docker-puppet-ironic_api", ... ... And it finally fails with ironic container: 2018-11-05 13:45:34 | "2018-11-05 13:43:44,095 ERROR: 10577 -- Failed running docker-puppet.py for ironic", 2018-11-05 13:45:34 | "2018-11-05 13:43:44,096 ERROR: 10577 -- Notice: hiera(): Cannot load backend module_data: cannot load such file -- hiera/backend/module_da ta_backend", ... ... 2018-11-06 07:20:05 | "2018-11-06 07:18:11,730 ERROR: 29508 -- + mkdir -p /etc/puppet", 2018-11-06 07:20:05 | "2018-11-06 07:20:02,433 ERROR: 29503 -- ERROR configuring ironic", 2018-11-06 07:20:05 | ERROR: Heat log files: /var/log/heat-launcher/undercloud_deploy-_p_rT6 the containers-prepare-parameter.yaml file is filled with this content: parameter_defaults: DockerInsecureRegistryAddress: - 192.168.24.1:8787 ContainerImagePrepare: - push_destination: "192.168.24.1:8787" set: tag: "2018-11-04.3" namespace: "docker-registry.engineering.redhat.com/rhosp14" name_prefix: "openstack" name_suffix: "" ceph_namespace: "docker.io/ceph" ceph_image: "daemon" ceph_tag: "v3.1.0-stable-3.1-luminous-centos-7-x86_64" Version-Release number of selected component (if applicable): Puddle 2018-11-04.3 How reproducible: Always. Steps to Reproduce: 1. openstack undercloud install Actual results: Errors mentioned above. Expected results: Success. Additional info: sosreport on its way.