resolv.conf in containers set too late
Bug #1758144 reported by
Damian Cikowski
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
In Progress
|
Medium
|
Jesse Pretorius |
Bug Description
OSA 17.0.0 (Ubuntu)
I have `internal_
unbound_records:
- name: 'internal'
records:
- { host: internal.
I'm running infrastructure playbooks in default order: Unbound -> Repo install -> Haproxy and then `repo-use.yml` which is failing because resolvers addresses isn't yet set and load balancer internal address can't be resolved. It looks like resolv.conf should be set in all containers earlier.
Changed in openstack-ansible: | |
assignee: | nobody → Logan V (loganv) |
Changed in openstack-ansible: | |
assignee: | Logan V (loganv) → nobody |
Changed in openstack-ansible: | |
assignee: | nobody → Jesse Pretorius (jesse-pretorius) |
Changed in openstack-ansible: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
To post a comment you must log in.
It looks like `repo-use.yml` isn't compatible with JIT configuration of Unbound clients introduced in https:/ /github. com/openstack/ openstack- ansible/ commit/ b3c670faeba53eb 00212deb1e19749 9959c40561