[06:53] hi guys, someone online? [07:48] if I have an Ubuntu image which has already the nocloud-net file and I am trying to apply with Terraform something extra on the cloud-init user-data, does someone why is not working? [09:39] hi guys, someone online? [11:21] hi guys, someone online? [11:26] dante-as: genrally speaking there is always someone online, but maybe not someone who could answer your question. A better approach to the problem here is to simply ask your question and wait for someone to answer :) [11:26] (note - it might take a while to get an answer, since as you've noted not everyone gives full IRC attention all the time) [11:27] most people active on here are in american timezones, for the record [11:36] tribaal: thanks for the details :) [11:37] I'm having an Ubuntu image which has already nocloud-net embedded and I'm wondering if it's any way to add also a network configuration via cloud-init and Terraform for some VMs which use this image [12:08] our change to cloud-init was approved, what else do we need to do for it to be merged and included ? [12:08] https://code.launchpad.net/~adobrawy/cloud-init/+git/cloud-init/+merge/354679 [13:12] coli_: o/ I'm going to kick off a CI run against your branch. [13:13] Odd_Bloke: thank you. [13:14] Assuming that's all good, we should be able to land it in the next couple of days. [13:14] We're currently dealing with a regression in the last cloud-init snapshot we released to Ubuntu, so we're focused on that ATM. [13:15] Just to set expectations. :) [13:21] coli_: OK, we're seeing CI failures that are fixed in master, so you'll want to rebase onto (or merge from) master to get those fixes in. [13:21] coli_: Ping me once you've done so and I'll kick off another run. :) [13:56] blackboxsw: Once you're around: https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/373649 [14:31] smoser: If you're around, ^ is pretty urgent for us, it's breaking a bunch of production deploys. [14:32] smoser: blackboxsw: I'm also proposing that we upload this as a hotfix (i.e. https://github.com/cloud-init/qa-scripts/blob/master/doc/ubuntu_release_process.md#cherry-picked-changes) because I want to release the bare minimum on a Friday. [14:33] (And it's been made clear to us that the last SRU will be reverted if we can't address this today, which I would, of course, like to avoid. :) [15:08] Odd_Bloke: +1 on hotfix. I'm looking at your branch now [15:41] blackboxsw: https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/373655 [15:42] validating against what I build now Odd_Bloke [15:44] Odd_Bloke: my only diff is expected https://paste.ubuntu.com/p/fd8zmgKdZN/ [15:44] awaiting tox and we can manually merge into ubuntu/bionic [15:45] I may drop into hangout so we can pair/discuss if needed [15:45] blackboxsw: https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/373656 [15:45] blackboxsw: No need to merge, I'll just upload and push. [15:47] approved https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/373655 [15:49] Odd_Bloke: one sec [15:49] blackboxsw: What's up? [15:50] ahh you are good on ubuntu/bionic I botched the package version name with 19.2-36-g059d049c-0ubuntu1~18.04.1ubuntu1 instead of 19.2-36-g059d049c-0ubuntu1~18.04.1 [15:51] I had seen that extra line diff between our branches, but you did it correctly [15:52] OK, good. [15:52] Odd_Bloke: approved again https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/373655 [15:53] Odd_Bloke: approved ubuntu/devel only metadata diff https://paste.ubuntu.com/p/GxK6rMFZp3/ [15:55] Thanks! [15:55] blackboxsw: https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/373657 is next up [15:57] approved disco https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/373657 [16:02] Odd_Bloke: I'm ready for xenial when you are [16:06] blackboxsw: Yep, working on it. [16:06] Ran into orig tarball mismatches, so had to regenerate my local packages. [16:08] blackboxsw: https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/373660 [16:08] ahh roger, happened to me yesterday [16:09] approved https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/373660 [16:10] I see you've pushed eoan good good [16:13] Old_Bloke: rebased to master, tested on 18.10 and 19.10 no issues noticed. [16:13] https://code.launchpad.net/~adobrawy/cloud-init/+git/cloud-init/+merge/354679 [16:41] Old_Bloke: can you kick off another run of CI against our branch (above) ? [16:43] will do cll [16:43] coli_: [16:44] CI rebuild kicked [17:35] Odd_Bloke: sorry, wasnt around. just saw. i think you're sorted now. [17:58] smoser: Yep, thanks! [17:59] blackboxsw: thank you. === rezroo1 is now known as rezroo [23:03] I'm trying to make my first changes to the cloud-init project. Is https://jenkins.ubuntu.com publicly available? Today, at different times of the day, I tried and couldn't access (timeout). [23:03] DobrawyAdam: Unfortunately, it isn't. [23:04] It was, but recent Jenkins vulnerabilities have meant that our security team aren't comfortable having it public at all. [23:04] (We're in the process of migrating to a hosted system.) [23:04] Odd_Bloke: DobrawyAdam is a person who is responsible for the code in: https://code.launchpad.net/~adobrawy/cloud-init/+git/cloud-init/+merge/354679 [23:05] Could somebody provide me a build log for https://jenkins.ubuntu.com/server/job/cloud-init-autoland-test/359/ ? [23:06] DobrawyAdam: I can, but the issue is that our integration testing has gotten wedged, so I'm afraid there isn't anything you'll be able to do about it for now. [23:07] DobrawyAdam: https://paste.ubuntu.com/p/MMrCkxcT3y/ <-- there you go [23:08] We'll get that sorted on Monday, we're all into our weekends here (and are still around because of a critical issue, to boot >.>). [23:08] Thank you for your contributions, and sorry that the CI experience is so frustrating at the moment! [23:09] Odd_Bloke: can we help in some way ? [23:10] After reading the event log in general, I get the impression that the problem is beyond the scope of my patch. [23:11] Not really, though I appreciate the offer! [23:12] The fix itself wasn't too involved, we're just having to do manual testing across all the platforms that we have ready access to. [23:12] We're pretty much there, though. [23:13] Odd_Bloke: good luck then and hopefully you all will be able to enjoy weekend soon. We will get back to it next week. [23:13] Odd_Bloke: we are willing to help if these are some jobs like migrating the Jenkins which needs to be taken care of. [23:14] OK, great, we'll definitely bear that in mind! [23:14] Enjoy your weekend too! [23:17] Do you have knowledge of how providers perform continuous cloud-init integration tests with their platforms? I notice that tests/cloud_tests/platforms have integration tests only for EC2, KVM, LXD. [23:18] Those integration tests are run by us on the Jenkins infrastructure I just mentioned. [23:19] (They can run anywhere, they aren't tightly coupled to our infra.) [23:19] I understand that these are integration tests run by Cloud-init. I am thinking about other tests that run providers by self. [23:21] My patch has tests, but I'm afraid - due to the Cloud-init release cycle and all distributions release cycle - that the functionality will be broken and that the broken release will spread. [23:24] I don't know any specifics for other cloud providers, I'm afraid. [23:25] Thank you for the information. In that case, we will have to consider how to carry out such tests periodicly to react quickly, if our data source has been corrupted. [23:50] DobrawyAdam: we are definitely interested in having the cloud_tests extended to run against other platforms. so if you have interest in adding a new platform to cloud-init's test/cloud_tests [23:52] it would also help assist us in 1-off validation of needed in the future [23:53] What do you mean by "1-off validation"? [23:59] DobrawyAdam: When we're releasing cloud-init to existing Ubuntu releases, we do verification that it still works. If we have cloud_tests for a platform, that's a lot easier.