yahoo-eng-team team mailing list archive

[John A Meinel <john@xxxxxxxxxxxxxxxxx>]

Public bug reported:

I haven't quite figured out what is wrong, but I tried bootstrapping
bionic with Juju 2.3.6 (proposed) today. I had been successfully
bootstrapping on LXD bionic as of last week. This was my first attempt
to bootstrap on a MAAS image of bionic.

The cloud init version reported in /var/log/cloud-init-output.log is
listed as 18.2

(It may be that it has been "successfully" bootstrapping, but this error
has been in the logs and we just didn't notice it.)

Cloud-init v. 18.2 running 'modules:config' at Mon, 16 Apr 2018 05:51:08 +0000. Up 28.17 seconds.
2018-04-16 05:51:08,730 - util.py[WARNING]: Running module apt-configure (<module 'cloudinit.config.cc_apt_configure' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_apt_configure.py'>) failed
2018-04-16 05:51:08,930 - schema.py[WARNING]: Invalid config:
runcmd: ['set -xe', "mkdir -p '/var/lib/juju'\ncat > '/var/lib/juju/MAASmachine.txt' << 'EOF'\n'hostname: nuc7\n'\nEOF\nchmod 0755 '/var/lib/juju/MAASmachine.txt'", 'set -xe', "install -D -m 644 /dev/null '/etc/systemd/system/juju-clean-shutdown.service'", "printf '%s\\n' '\n[Unit]\nDescription=Stop all network interfaces on shutdown\nDefaultDependencies=false\nAfter=final.target\n\n[Service]\nType=oneshot\nExecStart=/sbin/ifdown -a -v --force\nStandardOutput=tty\nStandardError=tty\n\n[Install]\nWantedBy=final.target\n' > '/etc/systemd/system/juju-clean-shutdown.service'", "/bin/systemctl enable '/etc/systemd/system/juju-clean-shutdown.service'", "install -D -m 644 /dev/null '/var/lib/juju/nonce.txt'", "printf '%s\\n' 'user-admin:bootstrap' > '/var/lib/juju/nonce.txt'"] has non-unique elements


I wasn't able to easily figure out what the schema is for cloud-init, as it seems to be read from a file. I imagine it is available somewhere.

I don't know if we're doing something wrong, or if the schema is
incorrectly stating that "runcmd" cannot have the same bit of text
twice. I'm guessing its complaining because we pass "set -xe" in 2
different places?

** Affects: cloud-init
     Importance: Undecided
         Status: New

** Affects: juju
     Importance: Undecided
         Status: New

** Affects: juju/2.3
     Importance: High
         Status: Triaged


** Tags: bionic juju

** Also affects: juju
   Importance: Undecided
       Status: New

** Also affects: juju/2.3
   Importance: Undecided
       Status: New

** Changed in: juju/2.3
    Milestone: None => 2.3.6

-- 
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/1764264

Title:
  bionic cloud-init 18.2 refuses Juju's 'runcmd' stanza

Status in cloud-init:
  New
Status in juju:
  New
Status in juju 2.3 series:
  Triaged

Bug description:
  I haven't quite figured out what is wrong, but I tried bootstrapping
  bionic with Juju 2.3.6 (proposed) today. I had been successfully
  bootstrapping on LXD bionic as of last week. This was my first attempt
  to bootstrap on a MAAS image of bionic.

  The cloud init version reported in /var/log/cloud-init-output.log is
  listed as 18.2

  (It may be that it has been "successfully" bootstrapping, but this
  error has been in the logs and we just didn't notice it.)

  Cloud-init v. 18.2 running 'modules:config' at Mon, 16 Apr 2018 05:51:08 +0000. Up 28.17 seconds.
  2018-04-16 05:51:08,730 - util.py[WARNING]: Running module apt-configure (<module 'cloudinit.config.cc_apt_configure' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_apt_configure.py'>) failed
  2018-04-16 05:51:08,930 - schema.py[WARNING]: Invalid config:
  runcmd: ['set -xe', "mkdir -p '/var/lib/juju'\ncat > '/var/lib/juju/MAASmachine.txt' << 'EOF'\n'hostname: nuc7\n'\nEOF\nchmod 0755 '/var/lib/juju/MAASmachine.txt'", 'set -xe', "install -D -m 644 /dev/null '/etc/systemd/system/juju-clean-shutdown.service'", "printf '%s\\n' '\n[Unit]\nDescription=Stop all network interfaces on shutdown\nDefaultDependencies=false\nAfter=final.target\n\n[Service]\nType=oneshot\nExecStart=/sbin/ifdown -a -v --force\nStandardOutput=tty\nStandardError=tty\n\n[Install]\nWantedBy=final.target\n' > '/etc/systemd/system/juju-clean-shutdown.service'", "/bin/systemctl enable '/etc/systemd/system/juju-clean-shutdown.service'", "install -D -m 644 /dev/null '/var/lib/juju/nonce.txt'", "printf '%s\\n' 'user-admin:bootstrap' > '/var/lib/juju/nonce.txt'"] has non-unique elements

  
  I wasn't able to easily figure out what the schema is for cloud-init, as it seems to be read from a file. I imagine it is available somewhere.

  I don't know if we're doing something wrong, or if the schema is
  incorrectly stating that "runcmd" cannot have the same bit of text
  twice. I'm guessing its complaining because we pass "set -xe" in 2
  different places?

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