Bug 1907559
| Summary: | Standalone environment uses localhost for UC registry when first deployed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | James Parker <jparker> | ||||
| Component: | tripleo-ansible | Assignee: | OSP Team <rhos-maint> | ||||
| Status: | CLOSED ERRATA | QA Contact: | David Rosenfeld <drosenfe> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 16.1 (Train) | CC: | cjeanner, hbrock, jslagle, mburns | ||||
| Target Milestone: | beta | Keywords: | Triaged | ||||
| Target Release: | 17.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | tripleo-ansible-3.3.1-0.20220122230520.a2b01aa.el8ost | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-09-21 12:13:24 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: | |||||||
| Attachments: |
|
||||||
|
Description
James Parker
2020-12-14 17:40:40 UTC
Do not use push_destination: true in the container-image-prepare.yaml when deploying the all-in-one. Hello James, Would it be possible to provide the content of the /etc/hosts? Apparently there is a detection being done that wants to match the hostname on the ctlplane network, maybe it's just missing this bit (even for standalone).. Cheers, C. Hi Cédric,
Correct the ctlplane mapping is not present in the hosts file whenever I attempt to deploy for the first time on a newly provisioned beaker host. The subsequent deployment attempt will work since the /etc/hosts file is updated with the ctlplane network info. Info listed below.
Regards,
-James
# Before deploying
[root@intel-purley-lr-04 ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
# During first deploy attempt
......
jinja2 rendering roles Standalone
rendering j2 template to file: /home/stack/tripleo-heat-installer-templates/./puppet/standalone-role.yaml
No entry for intel-purley-lr-04.ctlplane in /etc/hosts. Falling back to use the default (localhost) undercloud registry.
No entry for intel-purley-lr-04.ctlplane in /etc/hosts. Falling back to use the default (localhost) undercloud registry.
** Performing Heat stack create.. **
.....
Exception: Deployment failed
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_deploy.py", line 1328, in _standalone_deploy
raise exceptions.DeploymentError('Deployment failed')
tripleoclient.exceptions.DeploymentError: Deployment failed
None
Not cleaning working directory /home/stack/tripleo-heat-installer-templates
Not cleaning ansible directory /home/stack/standalone-ansible-gqj_bg07
Install artifact is located at /home/stack/standalone-install-20201214170846.tar.bzip2
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Deployment Failed!
ERROR: Heat log files: /var/log/heat-launcher/undercloud_deploy-bza_001b
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Deployment failed.
# /etc/hosts has been updated with ctlplane mappings and second attempt to deploy will now work
[stack@intel-purley-lr-04 ~]$ cat /etc/hosts
# BEGIN ANSIBLE MANAGED BLOCK
192.168.24.101 intel-purley-lr-04.localdomain intel-purley-lr-04
192.168.24.101 intel-purley-lr-04.ctlplane.localdomain intel-purley-lr-04.ctlplane
# END ANSIBLE MANAGED BLOCK
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
10.46.9.32 rhos-qe-mirror-tlv.usersys.redhat.com download.lab.bos.redhat.com download.eng.bos.redhat.com download-node-02.eng.bos.redhat.com
Moving to OSP17 for now as we can probably address it for there. Given the standalone configuration is mostly for development purposes, we probably won't backport to 16.1. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2022:6543 |