/srv/irclogs.ubuntu.com/2019/08/23/#cloud-init.txt

parideOdd_Bloke, I've been able collect the logs of an i3.metal instance failing to reboot following your suggestion of attaching the volume to another instance13:26
parideOdd_Bloke, https://bugs.launchpad.net/cloud-init/+bug/184118213:26
ubot5Launchpad bug 1841182 in cloud-init "cloud-init fails when rebooting EC2 i3.metal instances" [Undecided,New]13:26
paridethere is my bug report13:26
Odd_BlokeThanks!13:28
blackboxswOdd_Bloke: or rharper if you get a chance to review my SRU branches into Xenial, Bionic and Disco, landing those are the only thing blocking us from moving forward with SRU Xenial: https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/371685 Bionic: https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/371686   Disco:15:53
blackboxswhttps://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/371687.   The only thing unique there is my enablement of Exoscale in debian/cloud-init.templates15:53
rharperright15:54
rharperblackboxsw: I looked at xenial/bionic, both have changelog entries mentioning enabling Aliyun, which I think you meant exoscale, right ?16:00
blackboxswrharper: grr right fixing16:02
blackboxswgit.lp is super slow again today16:15
blackboxswrharper: all fixed bionic xenial and disco debian/changelog s/AliYun/Exoscale16:45
blackboxswand retagged16:45
rharperok, I'll re review16:45
rharperblackboxsw: one more fix up on the sru branches in the cloud-init.templates18:17
blackboxswrharper: per the cloud-init.templates, there is a mix-n-match set of descriptions, some datasources say "Read from X metadata service", others say "X metadata services".18:44
rharper*shrug* ok18:44
blackboxswshall we update them all to be the same verbiage?18:44
rharperI wouldn't risk changing them18:44
rharperI'm not sure what happens if we do; isn't this debconf input or something ?18:44
blackboxsws/X metadata services/X metadata service/18:45
blackboxswrharper: that particular line item is just the human readable description that you can see in the 'ncurses' TUI if running dpkg-reconfigure18:45
blackboxswmaybe it's not ncurses anymore, but whatever the TUI is18:46
rharperso, we don't have to now; but I would like a tools/add-datasource script which manipulates/renders that file18:46
rharperthat way, we don't have to manually edit that file each time18:46
rharperblackboxsw: so I'll rereview and approve18:46
blackboxswpowersj: Odd_Bloke: just pushed sru templates to https://github.com/cloud-init/ubuntu-sru/tree/master/2019082319:07
powersjblackboxsw, thx!19:07
blackboxswOdd_Bloke: it's t-minus 0 mins until end of week your time, but if you end up grabbing one of the sru-related bugs listed in https://github.com/cloud-init/ubuntu-sru/tree/master/20190823 just let me know19:08
* blackboxsw was going to try looking at one of the cloud manual scripts to see if it needs to be extended to check for a specific bug in this release. (I imagine azure will have a bit)19:08
Odd_Blokeblackboxsw: Ack, will check in a few minutes if I think there's something I can take care of before EO[DWM].19:09
* blackboxsw queues xenial/bionic and disco sru 19:10
blackboxswOkie dokey SRU into xenial, bionic disco approved by vorlon. so it should be built shortly19:59
powersjwoohoo19:59
blackboxswtribaal: for next week there should be cloud images with updated cloud-init 19.2.21 with exoscale enabled. If you do get a chance to peek at it on your platform, feel free to comment on the SRU bug: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/184109920:00
ubot5Launchpad bug 1841099 in cloud-init (Ubuntu) "SRU cloud-init (19.1.1 to 19.2.21): Xenial, Bionic, and Disco" [Undecided,New]20:00
blackboxsw... it better be  well past tribaal's EOD20:00
blackboxswyou'll need to:    echo deb $mirror $(lsb_release -sc)-proposed main |20:02
blackboxsw       tee /etc/apt/sources.list.d/proposed.list; apt-get update20:02
blackboxsw  mirror=http://archive.ubuntu.com/ubuntu20:04
Odd_Blokeblackboxsw: Cloud images won't include it until after the SRU is complete, right?  Or am I misunderstanding what you're asking tribaal to do?20:08
blackboxswOdd_Bloke: agreed. but <series>-proposed will have it. per my comment: echo deb $mirror $(lsb_release -sc)-proposed main |20:08
blackboxsw14:02        tee /etc/apt/sources.list.d/proposed.list; apt-get update20:08
Odd_Blokeblackboxsw: Right, but "there should be cloud images with updated cloud-init 19.2.21 with exoscale enabled" is misleading, I think?20:09
blackboxswtribaal: will need to add a <series-name> proposed apt-source to his instances to see and install updated cloud-init-19.2.21 and then run "sudo cloud-init clean --reboot  --logs" to exercise the updated cloud-init20:09
blackboxswOdd_Bloke: ahh right sorry tribaal. That is misleading. there are a couple of steps to enable that new -proposed cloud-init in the image; 1. add <series>-proposed apt source;  2. apt-get update; 3. sudo apt-get install cloud-init; 4: sudo cloud-init clean --reboot --logs;20:10
blackboxswwe run the following script on a new vm https://github.com/cloud-init/ubuntu-sru/blob/master/bugs/lp-1797480.txt#L17-L2320:13
blackboxswfollowed by cloud-init clean --logs --reboot.   given that a new datasource is enabled, you might have to add  Exoscale to /etc/cloud/cloud.cfg.d/90_dpkg.cfg20:14
blackboxswor dpkg-reconfigure cloud-init20:14
Odd_BlokeDo we have docs on how to do this?20:15
blackboxswOdd_Bloke: I can add something to our SRU docs if needed, but we do have the following: https://cloudinit.readthedocs.io/en/latest/topics/datasources.html?highlight=datasource_list#adding-a-new-datasource20:27
blackboxsw"Add your datasource name to the builtin list of datasources:" and "Enable datasource by default in ubuntu packaging branches:"20:27
Odd_Blokeblackboxsw: I meant specifically on how people can test cloud-init from -proposed for us.20:43
blackboxswOdd_Bloke: I'll add a trello card, yeah we should add new section on the testing/debugging page simple on https://cloudinit.readthedocs.io/en/latest/topics/debugging.html21:00
blackboxswrharper: yeah for openstack network v2 I'll have to address network_state passthrough for v2 IBMCloud, ConfigDrive or OpenStack all use the adapted cloudinit.sources.helpers.openstack.py:convert_net_json helper to create NetworkState  instances. So, it looks like this branch will be a bit bigger :/22:18

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!