Overcloud nodes are not reachable from undercloud by short hostname

Bug #1881708 reported by Cédric Jeanneret
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Incomplete
Medium
Cédric Jeanneret

Bug Description

A regression was introduced with https://review.opendev.org/#/c/705634/: access from the UC to the OC using shortname doesn't work anymore, because the shortname points to the internalapi IP.

This was first reported on Red Hat bugzilla[1] and affects Train and later releases.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1840994

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-ansible (master)

Fix proposed to branch: master
Review: https://review.opendev.org/732491

Changed in tripleo:
status: Triaged → In Progress
Revision history for this message
Harald Jensås (harald-jensas) wrote :

So, users did something manually, and it no longer works.
The workaround is simply to suffix the shortname with '.ctlplane'.
   Instead of doing:
     $ ssh overcloud-controller-0
   Now need to do:
     $ ssh overcloud-controller-0.ctlplane
       (alternatively use the FQDN overcloud-controller-0.ctlplane.cloud_name)
     $ ssh overcloud-controller-0.external
       (alternatively use the FQDN overcloud-controller-0.external.cloud_name)

We could try to render /etc/hosts per role, and stick the shortname alias on the hostname resolve network of each role. But the logic is complex, the risk of breaking something is high.

I think we should make this a documentation bug.
Manually creating hosts entries no longer work, users need to be explicit about which interface they want to connect to by including the .$NETWORK suffix when they ping/ssh etc overcloud nodes from the undercloud.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tripleo-ansible (master)

Change abandoned by Cédric Jeanneret (Tengu) (<email address hidden>) on branch: master
Review: https://review.opendev.org/732491
Reason: There are too many unwanted outcomes with this kind of change. It's better to actually document the "new" behavior introduced by 76fd2eaacc202ab5681d23596ed0f3d25216bb9f and advice to add what network we want to reach (hostname.ctlplane, hostname.internalapi, and so on).

Changed in tripleo:
milestone: victoria-1 → victoria-3
Changed in tripleo:
milestone: victoria-3 → wallaby-1
Changed in tripleo:
milestone: wallaby-1 → wallaby-2
Changed in tripleo:
milestone: wallaby-2 → wallaby-3
Changed in tripleo:
milestone: wallaby-3 → wallaby-rc1
Changed in tripleo:
milestone: wallaby-rc1 → xena-1
Changed in tripleo:
milestone: xena-1 → xena-2
Revision history for this message
Marios Andreou (marios-b) wrote :

This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo

Changed in tripleo:
milestone: xena-2 → none
status: In Progress → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.