diff options
| author |   Steve Baker <sbaker@redhat.com> | 2016-12-06 16:27:04 +1300 |
|---|---|---|
| committer | Steve Baker <sbaker@redhat.com> | 2016-12-08 20:09:25 +0000 |
| commit | bb73874310ce7a7a2a7da6a848dbd60e4e0aff12 (patch) | |
| tree | cdd02b4b04c36b2c01aae1338548cab1fbcf0d35 /puppet/services/mistral-executor.yaml | |
| parent | 1e11997e76a0d4dfba7909ad242882ef91967b4e (diff) | |
docker: don't use custom run-os-net-config
The script run-os-net-config[1] copies in ifcfg-* from the host before
running os-net-config. Apparently it was done this way because the
other scripts in /etc/sysconfig/network-scripts/ differed between host
and agent container. This should be less of an issue now that host and
heat-agents run centos-7 (even when the host is atomic)
tripleo-heat-templates recently changed to running os-net-config in a
deployment script instead of an os-refresh-config script [2]. This
means that our current run-os-net-config approach is currently
resulting in os-net-config being executed twice.
Another issue with run-os-net-config is that it copies ifcfg-* from
host to container, but not back again. This means that rebooting the
server will result in unconfigured interfaces until os-net-config is
somehow run again.
This change bind mounts /etc/sysconfig/network-scripts/ from the host
and uses the conventional approach to running os-refresh-config.
This may fix the issue where compute nodes are losing network
connectivity, so
Closes-Bug: #1646897
[1] http://git.openstack.org/cgit/openstack/tripleo-common/tree/heat_docker_agent/run-os-net-config
[2] I0ed08332cfc49a579de2e83960f0d8047690b97a
Change-Id: I763fc8d8e3eb10ac64d33e46c92888d211003e72
Diffstat (limited to 'puppet/services/mistral-executor.yaml')
0 files changed, 0 insertions, 0 deletions