/srv/irclogs.ubuntu.com/2018/05/24/#cloud-init.txt

smoserblackboxsw: nice. i was just about to do that... came in to just go ahead and do an upload00:24
smoserblackboxsw: http://paste.ubuntu.com/p/RfPQ3MDVH7/ ? for review-mps ?14:57
smoseri could not figure out how to '--skip' more stuff...14:57
smoserand --dry-run doesn't work so well because it dry-runs everything (even necessary read-only operations)14:58
=== dhill is now known as Guest96125
blackboxswsmoser, I'm adding an alias, dryrun == skip(bugs,publish,test)... only validate/lint the branch and print errors locally (no remote changes)18:28
smosersounds good.18:29
blackboxswI should've changed dryrun when introducing skip bugs, publish, test ... just didn't get around to it18:29
robjosmoser: https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/346844  should address parts of lp#109263719:08
smoseri think you typod that number19:09
smoserbug 177296119:09
ubot5bug 1772961 in cloud-init "suse (packages/suse/cloud-init.spec.in) spec does not build" [Medium,Confirmed] https://launchpad.net/bugs/177296119:09
smoser?19:09
robjotoo many bugs in my Inbox :( , yes cut and paste error19:16
=== rcj is now known as Guest73979
=== seba is now known as Guest82233
=== x58 is now known as Guest37083
=== Guest73979 is now known as rcj
smoserrobjo: it looks like you still need the 4 changes in https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+ref/fix/1772961-suse-spec-fixes19:35
smoserand then we get to19:35
smoser http://paste.ubuntu.com/p/gZpTmTW3jN/19:35
smoserrobjo: thanks for looking at that.19:39
robjosmoser: my changes were only to address the "missing files" issue, i.e. addition to what you had already done19:40
smoserah. ok. well, just grab my commits too and take over that branch.19:40
smoserif you'd like i can quickly give you access to an instance that you can use 'run-container' from.19:40
robjosorry still poking around while keeping an eye on the last of the Specter v4 image publishing19:43
=== dhill is now known as Guest64332
blackboxswok so changes that we landed in cloud-init for salt support freebsd changed the way /etc/salt/pki minion certs are created. Docs (https://docs.saltstack.com/en/2017.7/ref/configuration/minion.html#pki-dir)  still claim that the minion certs should live under /etc/salt/pki/minion  path, but cloud-init now checks isdir(/etc/salt/pki/minion )  and opts to use just /etc/salt/pki if minion subdir isn't present. This breaks20:24
blackboxswon ubuntu as those invalid certs in /etc/salt/pki/* are deleted. But, apparently that is intended behavior on FreeBSD. I need to find out why these files are being removed by a 'system salt-minion restart' on bionic++20:24
* blackboxsw is trying to resolve https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/176975420:26
ubot5Ubuntu bug 1769754 in cloud-init (Ubuntu) "salt-minion: public/private keys not preserved in /etc/salt/pki" [Undecided,New]20:26

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