Since /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg is rewritten at every boot with a cloud-init network section, any network section added to /etc/cloud/cloud.cfg will be overridden and have no effect.
A workaround for MAAS deployed CentOS images would be:
1) Log into the affected CentOS server
2) Replace the contents of /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg with the following:
network:
config: disabled
3) Make the file immutable by running:
sudo chattr +i /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg
4) Verify success of above command by running:
lsattr /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg
Output should look like this:
----i--------e-- /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg
Addendum to comment #8
Since /etc/cloud/ cloud.cfg. d/50-curtin- networking. cfg is rewritten at every boot with a cloud-init network section, any network section added to /etc/cloud/ cloud.cfg will be overridden and have no effect.
A workaround for MAAS deployed CentOS images would be: cloud.cfg. d/50-curtin- networking. cfg with the following:
1) Log into the affected CentOS server
2) Replace the contents of /etc/cloud/
network:
config: disabled
3) Make the file immutable by running: cloud.cfg. d/50-curtin- networking. cfg cloud.cfg. d/50-curtin- networking. cfg
sudo chattr +i /etc/cloud/
4) Verify success of above command by running:
lsattr /etc/cloud/
Output should look like this: -i----- ---e-- /etc/cloud/ cloud.cfg. d/50-curtin- networking. cfg
---