Re: [atomic-devel] Setting a DNS entry

[Charlie Drage <cdrage redhat com>]

Seems that resolv doesn't work correctly. I'm getting an ambiguous
error within /var/boot/log, despite having valid yaml

My cloud-init:
#cloud-config
hostname: cloud

manage-resolv-conf: true
resolv_conf: 
  nameservers: 
    - "8.8.4.4"
    - "8.8.8.8"
ssh_authorized_keys: 
  - "ssh_key_goes_here"

ssh_pwauth: false

cat /var/log/boot.log:
[  OK  ] Started Network Manager Script Dispatcher Service.
[    5.996390] cloud-init[647]: 2016-03-16 16:59:09,683 - util.py[WARNING]: Failed loading yaml blob
[    6.030294] cloud-init[647]: 2016-03-16 16:59:09,717 - util.py[WARNING]: Failed loading yaml blob
[    6.034553] cloud-init[647]: 2016-03-16 16:59:09,721 - util.py[WARNING]: Failed at merging in cloud config part from part-001
         Starting Hostname Service...
[  OK  ] Started Hostname Service.
[  OK  ] Started Initial cloud-init job (pre-networking).
...


On 03/15, Charlie Drage wrote:
> Thank you so much everyone for the feedback! It really helps.
> 
> I'm going to debug / test the resolv.conf issues. It seems that when
> setting a public IP it screws up at times (I'll have to identify
> what's happening within /var/log/boot.log
> 
> In regards to the port Colin, is there a place / github / git repo
> where I can contribute to the fixing of the port?
> 
> On 03/15, Colin Walters wrote:
> > 
> > 
> > On Mon, Mar 14, 2016, at 06:19 PM, Charlie Drage wrote:
> > > My meta-data I use this:
> > > 
> > > instance-id: Atomic02
> > > local-hostname: atomic-host-002
> > > network-interfaces: |
> > 
> > I'd recommend against using the cloud-init network-interfaces stanza.  It's
> > in a messy state of porting against "redhat-initscripts" network configuration
> > vs NetworkManager (and then against systemd-networkd...).
> > 
> > > I'm forced to use in cloud-config
> > > 
> > > #cloud-config
> > > bootcmd:
> > >  - echo 8.8.8.8  > /etc/resolv.conf
> > 
> > I don't see a serious problem with using `bootcmd`.  The broader role
> > of cloud-init should just be a bootstrap tool for authentication and such
> > in order to set up a better systems management tool like Ansible.
> > 
> > > Unfortunatley after a reboot resolv.conf is removed due to network
> > > manager autogenerating the resolv.conf file.
> > 
> > See https://github.com/openshift/training/issues/193#issuecomment-120496871
> > for an example of setting dns=none.
> > 
> 
> -- 
> 
> Charlie Drage
> Red Hat - OSAS Team / Project Atomic
> 4096R / 0x9B3B446C
> http://pgp.mit.edu/pks/lookup?op=get&search=0x622CDF119B3B446C
> 

-- 

Charlie Drage
Red Hat - OSAS Team / Project Atomic
4096R / 0x9B3B446C
http://pgp.mit.edu/pks/lookup?op=get&search=0x622CDF119B3B446C