yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1394061@xxxxxxxxxxxxxxxxxx>]

[Expired for cloud-init because there has been no activity for 60 days.]

** Changed in: cloud-init
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1394061

Title:
  unable to set resolve.conf

Status in cloud-init:
  Expired

Bug description:
  # The top level settings are used as module
  # and system configuration.

  # A set of users which may be applied and/or used by various modules
  # when a 'default' entry is found it will reference the 'default_user'
  # from the distro configuration specified below
  users:
     - default

  # If this is set, 'root' will not be able to ssh in and they
  # will get a message to login instead as the above $user (ubuntu)
  disable_root: true

  locale: en_US.UTF-8
  apt_preserve_sources_list: true

  # This will cause the set+update hostname module to not operate (if true)
  preserve_hostname: true

  manage_etc_hosts: false
  manage-resolv-conf: true

  resolv_conf:
    nameservers: ['208.67.222.222', '127.0.0.1', '208.67.220.220']
    searchdomains:
      - my.domain.net
    domain: domain.net
    options:
      rotate: true
      timeout: 1

  # write_files:
  #  - path: /etc/resolv.conf
  #    permissions: 0644
  #    owner: root
  #    content: |
  #      nameserver 208.67.222.222
  #      nameserver 127.0.0.1
  #      nameserver 208.67.220.220

  # Example datasource config
  # datasource:
  #    Ec2:
  #      metadata_urls: [ 'blah.com' ]
  #      timeout: 5 # (defaults to 50 seconds)
  #      max_wait: 10 # (defaults to 120 seconds)

  # The modules that run in the 'init' stage
  cloud_init_modules:
   - migrator
   - seed_random
   - bootcmd
   - write-files
   - growpart
   - resizefs
   - set_hostname
   - update_hostname
   - update_etc_hosts
   - ca-certs
   - rsyslog
   - users-groups
   - ssh
  # - resolv_conf

  # The modules that run in the 'config' stage
  cloud_config_modules:
  # Emit the cloud config ready event
  # this can be used by upstart jobs for 'start on cloud-config'.
   - emit_upstart
   - disk_setup
   - mounts
   - ssh-import-id
   - locale
   - set-passwords
   - grub-dpkg
   - apt-pipelining
   - apt-configure
   - package-update-upgrade-install
   - landscape
   - timezone
   - puppet
   - chef
   - salt-minion
   - mcollective
   - disable-ec2-metadata
   - runcmd
   - byobu

  # The modules that run in the 'final' stage
  cloud_final_modules:
   - rightscale_userdata
   - scripts-vendor
   - scripts-per-once
   - scripts-per-boot
   - scripts-per-instance
   - scripts-user
   - ssh-authkey-fingerprints
   - keys-to-console
   - phone-home
   - final-message
   - power-state-change

  # System and/or distro specific settings
  # (not accessible to handlers/transforms)
  system_info:
     # This will affect which distro class gets used
     distro: ubuntu
     # Default user name + that default users groups (if added/used)
     default_user:
       name: admin
       lock_passwd: false
       gecos: Ubuntu
       groups: [adm, audio, cdrom, dialout, dip, floppy, netdev, plugdev, sudo, video]
       sudo: ["ALL=(ALL) NOPASSWD:ALL"]
       shell: /bin/bash
     # Other config here will be given to the distro class and/or path classes
     paths:
        cloud_dir: /var/lib/cloud/
        templates_dir: /etc/cloud/templates/
        upstart_dir: /etc/init/
     ssh_svcname: ssh

  For some off reason resolv.conf get keep getting overwritten by
  resolvconf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1394061/+subscriptions