Unable to bootstrap pacemaker cluster when undercloud is containerized with ipv6 overcloud
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Emilien Macchi |
Bug Description
Environment: featureset035 (3 controllers, 1 compute, ipv6 control plane) with containerized undercloud
The deployment fails at step 1:
https:/
When bootstrapping the pacemaker cluster:
https:/
Error: Unable to communicate with overcloud-
Error: Unable to communicate with overcloud-
Error: Unable to communicate with overcloud-
It only fail when you try to enable the containerized undercloud.
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → rocky-2 |
tags: | added: containers |
Changed in tripleo: | |
assignee: | nobody → Emilien Macchi (emilienm) |
Changed in tripleo: | |
status: | Triaged → In Progress |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Changed in tripleo: | |
status: | In Progress → Fix Committed |
Changed in tripleo: | |
status: | Fix Committed → Fix Released |
Jun 03 03:22:03 overcloud- controller- 0 systemd[1]: pcsd.service start operation timed out. Terminating. controller- 0 ntpd_intres[30308]: host name not found: pool.ntp.org controller- 0 systemd[1]: Failed to start PCS GUI and remote configuration interface. controller- 0 systemd[1]: Unit pcsd.service entered failed state. controller- 0 systemd[1]: pcsd.service failed. controller- 0 puppet-user[29328]: Systemd start for pcsd failed!
Jun 03 03:22:24 overcloud-
Jun 03 03:22:26 overcloud-
Jun 03 03:22:26 overcloud-
Jun 03 03:22:26 overcloud-
Jun 03 03:22:26 overcloud-
So this is the usual 'pcsd needs a dns to not time out requests to work'. So we likely are timing out dns queries...
https:/ /logs.rdoprojec t.org/16/ 566916/ 11/openstack- check/gate- tripleo- ci-centos- 7-ovb-3ctlr_ 1comp-featurese t035-master/ Zb3297f9fb4a44a 10b34f7afa1b9e8 60d/overcloud- controller- 0/etc/resolv. conf.txt. gz has: dhclient- script
; generated by /usr/sbin/
search localdomain
nameserver 38.145.33.91
nameserver 38.145.32.66
nameserver 38.145.32.79
So https:/ /logs.rdoprojec t.org/16/ 566916/ 11/openstack- check/gate- tripleo- ci-centos- 7-ovb-3ctlr_ 1comp-featurese t035-master/ Zb3297f9fb4a44a 10b34f7afa1b9e8 60d/overcloud- controller- 0/var/log/ host_info. txt.gz has:
+ ip route
default via 192.168.24.1 dev eth0
169.254.169.254 via 192.168.24.1 dev eth0
172.16.0.0/24 dev br-tenant proto kernel scope link src 172.16.0.10
172.31.0.0/24 dev docker0 proto kernel scope link src 172.31.0.1
192.168.24.0/24 dev eth0 proto kernel scope link src 192.168.24.17
So I presume the undercloud when deployed via containers is blocking something around udp/tcp 53 (DNS) ?