Designate DNS IPv6 - Overcloud deploy fails on "Clean up legacy Cinder keystone catalog entries" step

Bug #2011476 reported by Brent Eagles
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
In Progress
High
Brent Eagles

Bug Description

Originally reported as https://bugzilla.redhat.com/show_bug.cgi?id=2156725

"I've created a new Designate CI job with the changes needed to support IPv6 (ir_tripleo_overcloud_network_protocol: 'ipv6')[1].
Unfortunately, the job failed on the "Overcloud" stage[2]:

 FATAL | Clean up legacy Cinder keystone catalog entries | undercloud | item={'service_name': 'cinderv2', 'service_type': 'volumev2'} | error={"ansible_index_var": "cinder_api_service", "ansible_loop_var": "item", "changed": false, "cinder_api_service": 0, "item": {"service_name": "cinderv2", "service_type": "volumev2"}, "module_stderr": "Failed to discover available identity versions when contacting http://[2620:52:0:13b8:5054:ff:fe3e:46]:5000. Attempting to parse version from URL.\nTraceback (most recent call last):\n File \"/usr/lib/python3.9/site-packages/urllib3/connection.py\", line 169, in _new_conn\n conn = connection.create_connection(\n File \"/usr/lib/python3.9/site-packages/urllib3/util/connection.py\", line 96, in create_connection\n raise err\n File \"/usr/lib/python3.9/site-packages/urllib3/util/connection.py\", line 86, in create_connection\n sock.connect(sa)\nOSError: [Errno 113] No route to host\n\nDuring handling of the above exception, another exception occurred"

Revision history for this message
Brent Eagles (beagles) wrote :

Setting an /128 IPv6 address on the external network interface seems to confuse something in the haproxy endpoint configuration deployment issues.

Changed in tripleo:
milestone: none → zed-1
status: New → Triaged
importance: Undecided → High
assignee: nobody → Brent Eagles (beagles)
Revision history for this message
Brent Eagles (beagles) wrote :

A possible workaround is to defer designate's IP configuration for bind until after haproxy has had it's turn in step 3. A better solution would be to figure out how to get it haproxy's config to work without it having to be first

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (master)
Changed in tripleo:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-ansible (stable/wallaby)

Fix proposed to branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/tripleo-ansible/+/880768

Brent Eagles (beagles)
tags: added: wallaby-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tripleo-heat-templates (master)

Change abandoned by "Brent Eagles <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/877322
Reason: better fix here https://review.opendev.org/c/openstack/tripleo-ansible/+/880768

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.