[00:00] <jchevalier> (I'll let my computer on non-stop to avoid any message lost)
[00:07] <jchevalier> If anyone has more infos, I try to install cloud-init on SLES to create an cloud-init ready image on AZure
[11:19] <amitprakash> Can someone please help me make sense of why cloud-init is failing? https://gist.github.com/291e61880cfdc6c9e1bc46b243d47760 I've verified that /bin/ip exists
[11:20] <amitprakash> Modifying net/*.py with abspath to binaries allows it to find ip/resize2fs etc commands
[11:20] <amitprakash> any ideas why the path is broken for cloud-init
[14:14] <smoser> amitprakash: where is this ?
[14:16] <smoser> what environment ? cloud-init just gets the PATH that init gives it. one would think that systemd would have a sane PATH (including /bin)
[14:27] <amitprakash> smoser, custom ami for ec2
[14:27] <amitprakash> gentoo
[14:28] <amitprakash> brb
[16:28] <jchevalier> Hello everyone
[16:28] <jchevalier> I can't run a script at boot on my vm
[16:28] <jchevalier> But here what I have
[16:28] <jchevalier> test10:~ # cat /var/lib/cloud/instance/user-data.txt
[16:28] <jchevalier> Content-Type: multipart/mixed; boundary="[16:28] <jchevalier> MIME-Version: 1.0
[16:28] <jchevalier> --[16:28] <jchevalier> Content-Type: text/x-shellscript; charset="us-ascii"
[16:29] <jchevalier> MIME-Version: 1.0
[16:29] <jchevalier> Content-Transfer-Encoding: 7bit
[16:29] <jchevalier> Content-Disposition: attachment; filename="jchevalier.sh"
[16:29] <jchevalier> #!/bin/bash
[16:29] <jchevalier> touch /tmp/jchevalier
[16:29] <jchevalier> --[16:29] <jchevalier> test10:~ # cloud-init init
[16:29] <jchevalier> Cloud-init v. 0.7.8 running 'init' at Thu, 08 Feb 2018 16:22:46 +0000. Up 335.54 seconds.
[16:29] <jchevalier> ci-info: ++++++++++++++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++++++++++++
[16:29] <jchevalier> ci-info: +--------+------+-----------------------------+---------------+-------+-------------------+
[16:29] <jchevalier> ci-info: | Device |  Up  |           Address           |      Mask     | Scope |     Hw-Address    |
[16:29] <jchevalier> ci-info: +--------+------+-----------------------------+---------------+-------+-------------------+
[16:29] <jchevalier> ci-info: |   lo   | True |          127.0.0.1          |   255.0.0.0   |   .   |         .         |
[16:29] <jchevalier> ci-info: |   lo   | True |           ::1/128           |       .       |  host |         .         |
[16:29] <jchevalier> ci-info: |  eth0  | True |           10.0.0.8          | 255.255.255.0 |   .   | 00:0d:3a:1a:82:f1 |
[16:29] <jchevalier> ci-info: |  eth0  | True | fe80::20d:3aff:fe1a:82f1/64 |       .       |  link | 00:0d:3a:1a:82:f1 |
[16:29] <jchevalier> ci-info: +--------+------+-----------------------------+---------------+-------+-------------------+
[16:29] <jchevalier> ci-info: ++++++++++++++++++++++++++++++Route IPv4 info+++++++++++++++++++++++++++++++
[16:29] <jchevalier> ci-info: +-------+-----------------+----------+-----------------+-----------+-------+
[16:29] <jchevalier> ci-info: | Route |   Destination   | Gateway  |     Genmask     | Interface | Flags |
[16:29] <jchevalier> ci-info: +-------+-----------------+----------+-----------------+-----------+-------+
[16:30] <jchevalier> ci-info: |   0   |     0.0.0.0     | 10.0.0.1 |     0.0.0.0     |    eth0   |   UG  |
[16:30] <jchevalier> ci-info: |   1   |     10.0.0.0    | 0.0.0.0  |  255.255.255.0  |    eth0   |   U   |
[16:30] <jchevalier> ci-info: |   2   |  168.63.129.16  | 10.0.0.1 | 255.255.255.255 |    eth0   |  UGH  |
[16:30] <jchevalier> ci-info: |   3   | 169.254.169.254 | 10.0.0.1 | 255.255.255.255 |    eth0   |  UGH  |
[16:30] <jchevalier> ci-info: +-------+-----------------+----------+-----------------+-----------+-------+
[16:30] <jchevalier> test10:~ # Le script seemed to be loaded, and cloud-init does not raise an error, but the file is not created...
[16:30] <jchevalier> Any idea?
[16:42] <dpb1> jchevalier: use a pastebin next time. :)
[16:43] <jchevalier> Right my bad :)
[17:40] <smoser> jchevalier: can you post /run/cloud-init/status.json ?
[17:40] <smoser> i assume that one of the stages has not run.
[17:45] <jchevalier> https://paste.ubuntu.com/26542228/
[17:45] <jchevalier> hmm indeed
[18:16] <blackboxsw> smoser: did you already write an sru test case for one of the SRU features we are releasing? maas oauth maybe of OVF related. I thought I recalled something
[18:16] <blackboxsw> but I can't find the link
[18:20] <smoser> blackboxsw: i did the grub-legacy-ec2 one
[18:21] <smoser>  https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1581416
[18:21] <blackboxsw> ahh thank you
[18:22] <smoser> i will test that now
[18:30]  * blackboxsw will ping the authors on the SRU related bugs
[18:30] <blackboxsw> and pushing up my sru bug verification docs ubuntu-sru.
[18:31] <blackboxsw> think I'm missing a couple still
[18:31] <blackboxsw> almost there
[19:20] <jchevalier> Seems that the setup_disk module crashed the thing
[19:20] <jchevalier> but now I have to manually run cloud-init modules -m final
[19:21] <jchevalier> Otherwize the script in custom-data in not tun
[19:21] <jchevalier> run*
[19:21] <smoser> jchevalier: /var/log/cloud-init.log ?
[19:23] <jchevalier> https://paste.ubuntu.com/26542654/
[20:03] <smoser> jchevalier: what made you thnk setup_disk failed ?
[23:40] <blackboxsw> smoser: rharper found an SRU-blocker the identity doc stuff we landed  in ec2 doesn't work on upgrade path. self.identity doesn't exist on the pickled datasource