← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1855462] Re: Can't use advanced log configuration with Ubuntu and CloudStack

 

[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/1855462

Title:
  Can't use advanced log configuration with Ubuntu and CloudStack

Status in cloud-init:
  Expired

Bug description:
  System environment information: Apache CloudStack data source with
  VMWare hypervisor and a minimal Ubuntu 18.04 OS via net install from
  online mirror.

  #cloud-config

  datasource:
   CloudStack:
    max_wait: 120
    timeout: 50
    datasource_list:
     - CloudStack

  system_info:
   distro: ubuntu
   default_user:
    name: cloud
    lock_passwd: False
    sudo: ["ALL=(ALL) NOPASSWD:ALL"]

  disable_ec2_metadata: true
  ssh_pwauth: yes
  disable_root: true
  preserve_hostname: false

  output:
   init:
    output: ">> /var/log/cloud-init.out"
    error: ">> /var/log/cloud-init.err"
   config: ">> /var/log/cloud-config.log"
   final:
    - ">> /var/log/cloud-final.out"
    - ">>/var/log/cloud-final.err"

  packages:
   - ca-certificates
   - pastebinit

  
  Results:
  - networking is disabled, networkl interface is down
  - no cloud init log
  - no sudo rights for cloud user
  - hostname remains "localhost"
  - cloud-init status: disabled
  - cloud-init init: enforces cloud-init, with the following messages in the logs which then are created as desired in the config above.
  -> in "cloud-init.err": "No init modules to run under section cloud_init_modules"
  -> in "cloud-init.log": "finish: init-network: FAIL: searching for network datasources"

  
  To be sure, I've tested the YAML config and indented it in a way that yamllint produces only warnings, but no errors (a strict YAML would start with ---, not sure whether it would be ok in this context)

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


References