[10:34] <jchevalier> Hello
[10:35] <jchevalier> I struggle configuring cloud-init on azure with a SLES image, can anyone help me please?
[13:27] <jchevalier> Anyone is user cloud-init on azure ? I'd need some help to make it work!
[13:27] <jchevalier> thx
[14:50] <Odd_Bloke> jchevalier: It's better to just describe the problem you're having, rather than asking for help.
[14:50] <Odd_Bloke> People may come online later and be able to respond when you are idle.
[14:51] <Odd_Bloke> Or people may not want to respond without knowing the scope of what they're offering to help with. :)
[16:49] <mgerdts> I'm confused.  https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1667735 says that a fix was released, but I don't see anything in the bug that suggests in what release was fixed and I don't see anything in git log or git grep that mentions this bug.
[16:49] <ubot5> Ubuntu bug 1667735 in cloud-init (Ubuntu Trusty) "cloud-init doesn't retry metadata lookups and hangs forever if metadata is down" [Medium,Confirmed]
[16:50] <mgerdts> I certainly don't see the flush+negotiate in there, but that seems to be a separate issue from a timeout.
[17:32] <paulmey> jchevalier: I can help, hope you're still here... :-)
[17:33] <paulmey> smoser: is there an ETA for an SRU to get some of the bugfixes from the last two months into trusty/xenial/artful?
[17:41] <smoser> paulmey: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1747059
[17:41] <ubot5> Ubuntu bug 1747059 in cloud-init (Ubuntu Artful) "sru cloud-init (17.1.46-g7acc9e86-0ubuntu1) update to 17.2.30-gf7deaf15-0ubuntu1" [Medium,Confirmed]
[17:41] <smoser> paulmey: ^ that bug is the sru bug, so... its in progress.
[17:42] <blackboxsw> paulmey:  I'd guess ~2 weeks as that's how long our last SRU took
[17:42] <blackboxsw> and this is a pretty big SRU
[17:52] <paulmey> smoser: blackboxsw: yeah, we saved up a lot... :-)
[17:52] <paulmey> hence the question...
[17:52] <paulmey> but thanks, easy to track now
[18:36] <smoser> blackboxsw: i wrote a template for https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1581416
[18:36] <ubot5> Ubuntu bug 1581416 in cloud-init (Ubuntu Xenial) "grub-legacy-ec2 installs files in /etc/kernel/kernel/post(inst|rm).d" [Low,Confirmed]
[18:36] <smoser> i thikn we're good on bug statenow
[18:36] <blackboxsw> thanks smoser
[18:43] <mgerdts> @smoser - any comments on the bug I mentioned earlier?  It was closed by you.  https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1667735
[18:43] <ubot5> Ubuntu bug 1667735 in cloud-init (Ubuntu Trusty) "cloud-init doesn't retry metadata lookups and hangs forever if metadata is down" [Medium,Confirmed]
[18:44] <mgerdts> I don't know if was accidentally closed or I am just showing how much of a newbie I am with launchpad.
[18:50] <smoser> hm.
[18:51] <smoser> mgerdts: it looks in the right state.
[18:51] <mgerdts> The last comment says: Changed in cloud-init (Ubuntu):
[18:51] <mgerdts> status:	Fix Released → Confirmed
[18:52] <mgerdts> but above, it lists lots of releases where it's not fixed.  I'm having troubles decoding that.
[18:52] <mgerdts> I think an experiment I did last week suggests it's not fixed.
[18:53] <mgerdts> (not fixed in the 17.10 image for SmartOS, that is)
[18:54] <smoser> ok. so i think this is in the right state, a bit of launchpad education needed (i agree, it is confusing)
[18:55] <mgerdts> perhaps "Confirmed" is an earlier state than "fix released"
[18:55] <mgerdts> was accidentally set to fix released, then updated?
[18:55] <smoser> the 'cloud-init' task is the upstream project.  its not fixed in upstream, 'Confirmed' is the right state.
[18:55] <smoser> yeah, it was accidently changed i think.
[18:56] <smoser> the 'cloud-init (Ubuntu)' tracks if this bug affects "Ubuntu". which by default means "in the development release", which is currently bionic.
[18:56] <mgerdts> got it.  I had read that as it was fixed, then some testing was done to confirm that it was really fixed.
[18:56] <smoser> then there are 'Precise' and 'Trusty' tasks that are also Confirmed...
[18:56] <smoser> we could "also affects distribution/package" to add 'Xenial' and 'Bionic' specifically, but we dont really have to
[18:56] <smoser> and honestly i should just remove Precise becase we're never going to fix it there.
[18:56] <smoser> and probably not in trusty
[18:57]  * mgerdts needs to find the decoder ring for Ubuntu versions.
[18:57] <smoser> for your info... it'd take some pushing to get this fixed in trusty.
[18:57] <smoser> just due to age.
[18:58] <smoser> https://wiki.ubuntu.com/Releases
[19:00] <mgerdts> thanks... I didn't mean to suggest I was asking you to answer what google can answer quickly.
[20:28] <smoser> mgerdts: fix commit message to
[20:28] <smoser> a.) be Subject-Line\n<blank-line>\nmore-description
[20:29] <smoser> b.) reference your bugs with:
[20:29] <smoser>  LP: #BUG
[20:29] <smoser> (see examples in 'git log')
[20:29] <mgerdts> ok
[22:19] <jchevalier> I am trying to install cloud-init on SLES image for azure, but whatever I try 1- I can't connect through ssh keys ans 2- can't run a script with the custom-data parameter
[22:20] <jchevalier> What I tried :
[22:20] <jchevalier> Create a vm with the image SUSE:SLES:12-SP2:latest
[22:21] <jchevalier> Then install cloud-init following this: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/cloudinit-prepare-custom-image
[22:21] <jchevalier> Set cloud-init enabled through systemctl
[22:22] <jchevalier> Install packages to access ntfs partitions (I had errors in cloud-init log)
[22:22] <jchevalier> Then I deprovision the user with waagent
[22:23] <jchevalier> Finally, deallocate the vm, generalize it and create a image from it
[22:24] <paulmey> jchevalier: sounds like you're doing the right things...
[22:24] <jchevalier> Thx for answering
[22:25] <paulmey> enable boot diagnostics when you deploy your new cloud-init VM and take a look at the console output to see if there is anything interesting in there
[22:25] <jchevalier> I can do that from CLI?
[22:26] <paulmey> for some reason they have not implemented that yet
[22:26] <paulmey> you can enable it later, but that doesn't help you much
[22:27] <jchevalier> I'll try to create my vm from the dashboard
[22:27] <paulmey> or you can take a look at this example: https://github.com/Azure/azure-quickstart-templates/tree/master/101-vm-from-user-image
[22:27] <paulmey> I think you can also deploy that directly from github, but ymmv...
[22:30] <jchevalier> I get a look at the example
[22:56] <jchevalier> Re, sorry my connection is not as stable as I want
[23:12] <jchevalier> Here is the boot diagnostic result
[23:12] <jchevalier> [    0.000000] Initializing cgroup subsys cpuset [    0.000000] Initializing cgroup subsys cpu [    0.000000] Initializing cgroup subsys cpuacct [    0.000000] Linux version 4.4.103-92.56-default (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) #1 SMP Wed Dec 27 16:24:31 UTC 2017 (2fd2155) [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.4.103-92.56-default root=UUID=223f6e86-5f3c-46e4-84ec-fb8b064219af root=/dev/disk/by-
[23:12] <jchevalier> Oh, cr*p
[23:12] <jchevalier> too long
[23:14] <rharper> jchevalier: you may want to use paste.ubuntu.com  or other simple paste services for sharing
=== jchevalier_ is now known as jchevalier
[23:18] <jchevalier> Here the log
[23:18] <jchevalier> https://paste.ubuntu.com/26527141/
[23:18] <jchevalier> I can see that cloud-init has issues to find waagent