[00:04] <rharper> ecksit: I think if you create a user entry without a sudo: value in the dictionary, you won't get an entry for that user;  the sudoers file from cloud-init will get generated if the default user for your cloud-init has the sudo's group enabled, which it is in Ubuntu
[00:05] <rharper> it's also possible we've a bug, so could be worth filing an issue with an example of the user config you're using and what's happening, vs. what you expect
[00:10] <ecksit> you're right about neglecting the `sudo: value` bit but i was after an explicit way of saying that the user shouldn't have sudo instead.
[00:10] <ecksit> just in case `cloud-init` decides in the future to change the default
[00:14] <rharper> ecksit: we'd certainly consider it a bug to change the meaning of the sudo key in the user dictionary
[00:14] <rharper> but it's also reasonable to file a bug and request to allow sudo: false to be acceptable as a way to disable sudo entry for that user
[00:15] <ecksit> sure, where is the best place to lodge that? on launchpad?
[00:15] <rharper> yeah
[00:15] <rharper> https://bugs.launchpad.net/cloud-init/+filebug
[00:16] <ecksit> thanks, will take this there!
[00:41] <ecksit> lodged at https://bugs.launchpad.net/cloud-init/+bug/1771468 if anyone is following along at hme
[00:41] <ubot5> Ubuntu bug 1771468 in cloud-init "Allow a way to explicitly disable sudo for a user" [Undecided,New]
[00:45] <rharper> ecksit: thanks!
[00:46] <ecksit> my python is weak but i can attach a patch if that will get more eyes on it
[01:26] <blackboxsw> patches always welcome ecksit, we can help shepherd it in if there's an issue
[01:26] <blackboxsw> it'll definitely drive that feature faster if there is a patch proposed for it
[01:27] <ecksit> alright - i'll take a pass at it and see what i can do
=== r-daneel_ is now known as r-daneel
=== shardy_ is now known as shardy
[16:39] <blackboxsw> smoser: did you already push cloud-init 18.2.41 to cosmic?
[16:40] <blackboxsw> I'm guessing yes. rmadison thinks so L(
[16:40] <blackboxsw> I'm guessing yes. rmadison thinks so :) rather
[16:40] <blackboxsw> right that was last week Friday. ok
[17:19] <smoser> blackboxsw: i did do an upload to cosmic last week, yes,.
[18:50] <robjo> smoser: do we have a location for the summit? I'd like to find a hotel that's not too far away
[18:50] <smoser> robjo: we do. i didnt make that public, you'll get an invitaton sometime in the next couple weeks.
[18:51] <dpb1> smoser, robjo: I'm not sure we have a site nailed down yet.
[18:51] <dpb1> I mean, we know a company, but not a building.
[18:52] <robjo> OK thanks
[19:23] <smoser> robjo: i have nose running in an opensuse 42.3 container
[19:24] <smoser> the chef tets were all i had to fix (http and ssl related)
[19:26] <robjo> great, I will try and take a closer look at the failure I am seeing with test_apt_v3_mirror_search_dns
[19:44] <smoser> robjo: https://bugs.launchpad.net/cloud-init/+bug/1771659
[19:44] <ubot5> Ubuntu bug 1771659 in cloud-init "unittests fail in OpenSuSE 42.3 with httpretty issues" [Undecided,New]
[20:32] <smoser> powersj: you've probalby been over this, and i missed it.
[20:32] <smoser> "jenkins is going to shut down" ?
[20:32] <smoser> its not runnign tests now i dont think
[20:32] <powersj> yeah I put in an RT about it
[20:32] <powersj> waiting for IS
[20:45] <smoser> blackboxsw: https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/345630 is ready for review.
[21:07] <powersj> smoser: jenkins is up
[21:11] <smoser> powersj: htanks. i suspect run-container should work now.
[21:13] <smoser> its running https://jenkins.ubuntu.com/server/job/cloud-init-ci/1131/