resolv.conf in containers set too late

[Damian Cikowski]

OSA 17.0.0 (Ubuntu)

I have `internal_lb_vip_address` variable set to FQDN which is resolved by Unbound - additional record set using `unbound_records` variable:

unbound_records:
  - name: 'internal'
    records:
      - { host: internal.cloud.company.com, val: "{{ haproxy_keepalived_internal_vip_cidr | ipaddr('address') }}", type: A }

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.

[Damian Cikowski (dcdamien)]

It looks like `repo-use.yml` isn't compatible with JIT configuration of Unbound clients introduced in https://github.com/openstack/openstack-ansible/commit/b3c670faeba53eb00212deb1e197499959c40561

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/571178

[OpenStack Infra (hudson-openstack)]

Change abandoned by Jesse Pretorius (odyssey4me) (<email address hidden>) on branch: master
Review: https://review.opendev.org/571178
Reason: No longer working on this. Please restore this patch if it is still required.