[10:12] hiya, is it possible to run cloud-init with a test yaml-file that I'm debugging on the server? I have a file (test.yaml) that is under /root and I'd like to run it the same way a userdata-script would be ran. === cpaelzer_ is now known as cpaelzer === blackboxsw changed the topic of #cloud-init to: Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting: Monday 5/14 16:00 UTC | cloud-init 18.2 released (03/28/2018) [15:41] https://bugs.launchpad.net/cloud-init/+bug/1769690 [15:41] Ubuntu bug 1769690 in cloud-init "IBMCloud ds-identify detects NoCloud but cloud-init determines ConfigDrive " [Low,Confirmed] [15:42] unble to reproduce cloud-init clean reboot switch to NoCloud from ConfigDrive. may just be an Artful(unsupported by IBM images) thing [15:43] * blackboxsw heads to wrap up bionic SRU [16:59] good morning! I was hoping we could get https://code.launchpad.net/~paul-meyer/cloud-init/+git/cloud-init/+merge/344538 to a state where it can be merged... LMK what you want me to do. [17:05] paulmey: we can address this this week. rharper is out today (as he had initial thoughts on this branch I'll defer to him). [20:31] ok, I'll try to ping tomorrow morning then, but feel free to remind him. :-) Thanks! === meetingology` is now known as meetingology === holser___ is now known as holser_ === aimeeu__ is now known as aimeeu === blackboxsw_ is now known as blackboxsw [21:19] hrm just ran into this on bionic https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1769754 [21:19] Ubuntu bug 1769754 in cloud-init (Ubuntu) "salt-minion: public/private keys not preserved in /etc/salt/pki" [Undecided,New] [21:19] can't reproduce it across clean reboots, but just fresh installs. [21:20] it was affecting our clean intregration test runs on bionic [21:20] https://jenkins.ubuntu.com/server/job/cloud-init-integration-proposed-b/8/consoleFull [21:21] cloud-init in that case claimed to have written the pub/priv keys into /etc/salt/pki/* but the directory has a modification timestamp later than when the write took place (and the files are no longer there() [21:47] Hi, [21:51] oops, accidentally sent that, pls ignore :)