designate's named is conflicting with unbound in CI scenario003
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Ben Nemec |
Bug Description
After deployments on scenario003, we attempt to install dstat on the overcloud. Unfortunately it appears to be failing fairly regularly because it can't download the rpm.
2018-09-28 03:02:02.287193 | primary | PLAY [setup dstat performance monitoring] *******
2018-09-28 03:02:02.326067 | primary |
2018-09-28 03:02:02.326291 | primary | TASK [validate-perf : Install the latest version of dstat on overcloud] ********
2018-09-28 03:02:02.377924 | primary | Friday 28 September 2018 03:02:02 +0000 (0:00:00.331) 0:00:00.331 ******
2018-09-28 03:02:08.786581 | primary | fatal: [subnode-2]: FAILED! => {"changed": false, "msg": "http://
2018-09-28 03:02:08.786773 | primary | ...ignoring
I believe this is because named which is for designate may be causing issues.
udp6 0 0 :::53 :::* 82170/named
udp6 0 0 ::1:53 :::* 1755/unbound
udp6 0 0 ::1:53 :::* 1755/unbound
udp6 0 0 ::1:53 :::* 1755/unbound
udp6 0 0 ::1:53 :::* 1755/unbound
I'm a little surprised this is even allowed, but I think we can shut off BIND listening on localhost. The issue is I think it will break Designate functionality in ci because I used localhost as the predictable ip. If scenario003 isn't already using predictable ips we'll need to enable that so Designate knows where to look for BIND. This is good anyway since that's how Designate would be configured in real deployments, but it does complicate the fix for this problem.