The patch done via I989e3f1d14fd33e97933032111cf48166dc5f50c was
apparently not enough and we have seen cases where the /etc/resolv.conf
is still managed by NetworkManager (and DNS config nuked, causing
deployment issues).
This patch will use the `rc-manager` option and set to `unmanaged` which
will really force NM to unmanage this file.
Closes-Bug: #1958989
Change-Id: Ib6a3f384f32c6c4fbd577a5bee62db620401f850
(cherry picked from commit 9d0da2b383239d296b28ecb3b2458543dc0f0cb4)
Reviewed: https:/ /review. opendev. org/c/openstack /tripleo- ansible/ +/826556 /opendev. org/openstack/ tripleo- ansible/ commit/ 57422a1ac557c2a 5211a4d421e1148 4faf27634f
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/ussuri
commit 57422a1ac557c2a 5211a4d421e1148 4faf27634f
Author: Emilien Macchi <email address hidden>
Date: Tue Jan 25 08:39:09 2022 -0500
Force NetworkManager to unmanage /etc/resolv.conf
The patch done via I989e3f1d14fd33 e97933032111cf4 8166dc5f50c was
apparently not enough and we have seen cases where the /etc/resolv.conf
is still managed by NetworkManager (and DNS config nuked, causing
deployment issues).
This patch will use the `rc-manager` option and set to `unmanaged` which
will really force NM to unmanage this file.
Closes-Bug: #1958989 4fbd577a5bee62d b620401f850 96b28ecb3b24585 43dc0f0cb4)
Change-Id: Ib6a3f384f32c6c
(cherry picked from commit 9d0da2b383239d2