cloud-init resolv.conf not being setup

[vamfoom]

I have the following in my user-data file for cloud-init, but this doesn't seem to work:

Code: Select all

#cloud-config
manage_resolv_conf: true
resolv_conf:
  nameservers: ['10.1.1.100]
  searchdomains:
    - myawesomedomain.com
  domain: myawesomedomain.com
  options:
    rotate: true
    timeout: 1

But this is written in resolv.conf instead:

Code: Select all

# cat /etc/resolv.conf 
; Created by cloud-init on instance boot automatically, do not edit.
;
# Generated by NetworkManager
nameserver 10.0.2.3
search localdomain

I haven't the slightest clue where that IP came from. what am I missing?

[TrevorH]

# Generated by NetworkManager

Whatever was in there has been overwritten by NM when it started up. Check in /etc/sysconfig/network-scripts/ifcfg-* files for lines like DNS1= and remove them. If all else fails, add PEERDNS=no to them.

[vamfoom]

I figured it out after playing with it for a little while.

Turns out cloud-init by default doesn't run the resolv_conf module. I had to enable this module in cloud_config_module.

[desertcat]

I have the following in my user-data file for cloud-init, but this doesn't seem to work:

Code: Select all

#cloud-config
manage_resolv_conf: true
resolv_conf:
  nameservers: ['10.1.1.100]
  searchdomains:
    - myawesomedomain.com
  domain: myawesomedomain.com
  options:
    rotate: true
    timeout: 1

But this is written in resolv.conf instead:

Code: Select all

# cat /etc/resolv.conf 
; Created by cloud-init on instance boot automatically, do not edit.
;
# Generated by NetworkManager
nameserver 10.0.2.3
search localdomain

I haven't the slightest clue where that IP came from. what am I missing?

Just a quick heads up: I was prowling (that's what cats do) the RHEL 7.5 features, and from what I saw it is far more "cloud" intensive. CentOS is a clone of RHEL so I'm sure that CentOS 7.5 when it comes out within the next 4-8 weeks is likewise to be more "cloud" intensive as well. Stay tuned. For a preview of what you are likely to see in CentOS 7.5 look at the early reviews of RHEL 7.5

[vamfoom]

I figured out why resolv.conf was not being changed via cloud-init. Turns out the resolv_conf cloud-init module isn't enabled by default so you have to enable it. Ideally, every module should be enabled or at least a log entry should be made to indicate unknown module. Took me a couple of hours of trial-and-error plus googling.