Odd_Blokeblackboxsw: I think we should hold off on changes like that until we've investigated whether this is a lxd bug.01:12
Odd_Bloke(Gone again now; accidentally switched to this channel and would have forgotten to respond tomorrow morning without the highlight. :p)01:12
otuboSo I was writing a test for this PR: https://github.com/canonical/cloud-init/pull/70, which looks like this: https://pastebin.com/2z90v92F; and it started to fail on the most random place: https://pastebin.com/WSZcwMwB14:23
Odd_Blokeotubo: That looks to me like util.subp is being mocked without a return value.14:25
Odd_Blokeotubo: And, indeed, if you look at setUp in that class, that's what's happening.14:26
otuboOdd_Bloke: I knew I couldn't bypass all the functions that calls setup_swap, sorry about that.14:27
otuboOdd_Bloke: Actually I was trying to keep it simple and compact, calling only the function that it needs to be called, but I don't think that that's what's gonna happen :)14:28
otuboOdd_Bloke: thanks for the quick help!14:28
Odd_BlokeHappy to help!14:29
otuboOdd_Bloke: Ok I pushed the fixes from your comments, but the test I'm gonna leave for tomorrow probably :)14:54
meenarharper: my current chicken egg problem re system_info vs vendor-data is that to collect all vendor data, i'd need to get it from Hetzner which isn't properly recognized as such right now… despite being configured so… it's weird — it works on "first run" from boot, but not when run later…??14:56
meenai feel there's lots of inconsistencies in the code paths that cloud-init takes… on not-Linux.14:56
meenaso, for reasons incomprehensible to me, ds.meta_data is empty.14:58
meenaanyway, i'll post my collect-logs, and vendor-data output…14:59
Odd_Blokemeena: What do you mean by "isn't properly recognized as such"?15:00
meenabut perhaps this is just a transient problem until we solve https://github.com/canonical/cloud-init/pull/6115:00
meenaOdd_Bloke: cloud-init query cloud_name → none15:01
Odd_BlokeOh, right.15:02
meenahmmmm, yeah, def apply_network_config() is gone from Goneri's branch… i wonder if that's… a problem…15:03
Odd_Blokemeena: Is that on a subsequent boot, or first boot?  And do, e.g., Ubuntu images detect it correctly?15:03
meenaOdd_Bloke: subsequent, yes…15:04
meenaOdd_Bloke: i don't know, i've been working on this Fbsd thing… for… long.15:04
meenaalso, i'm working off of tip + mine + goneri's patches15:04
meenaso it's hard to say what's broken where 😅15:05
meenaalso, i'm dangerously overcaffeinated.15:05
smoserblackboxsw: why / where are you seeing errors with pstart ?15:05
smoserpstart should work. it should be valid. if its not, then we/I can/should fix it.15:06
Odd_Blokesmoser: You should be able to reproduce by running `lxd-proposed-snapshot disco -p disco-test-image` on a system with lxd 3.18.15:08
Odd_BlokeThis will successfully create the image, but instances launched from that image will have the wrong UID owning all the files.15:09
Odd_BlokeThis, of course, breaks everything. :p15:10
smoserits an lxd regression, they need to stop doing that.15:11
meenathe formatting on launchpad is so horrible… https://bugs.launchpad.net/cloud-init/+bug/185517015:13
ubot5Ubuntu bug 1855170 in cloud-init "system_info can change the distro" [Undecided,Incomplete]15:13
rharpersmoser: good luck with that ;  recall the last time we saw that with piping data to stdin;  https://github.com/lxc/lxd/issues/618815:14
rharper"sorry we broke your workload" p.s. actually not sorry15:14
smoserrharper is less restrained in his typing than I was.. ;)15:15
Odd_Blokemeena: https://imgflip.com/i/3j4d9s15:15
rharpersmoser: lol15:15
* rharper gets some coffee 15:16
smoserthe failure is dns?15:16
smoser(i hadnt seen a report or anything... just tried to recreate here)15:16
Odd_Blokesmoser: We've seen the failure manifest in a couple of ways, but we think they all boil down to incorrect UIDs.15:17
Odd_Blokeroot doesn't own the files it should, so a bunch of things are going to fail, it's just a case of which thing fails first.15:18
meenaOdd_Bloke: 😒15:18
Odd_Blokemeena: ^_^15:18
rharpersmoser: yeah the critical failure  (why we noticed) is that some files that systemd would work with aren't owned by root (they have uids/gids that aren't mapped correctly) so systemd refuses to use them; and networkd itself doesn't come up;  no networking means snapd fails and cloud-init can't ssh-import-id15:23
Odd_BlokeIt also breaks `lxc shell foo`, which is how I first noticed.15:24
Odd_BlokeFilled up the disk on my VM and now I can't remove any of the containers: Error: failed to begin transaction: failed to create dqlite connection: no available dqlite leader server found15:38
Odd_BlokeBanner day for lxd15:38
smoseri'm  not *sure* this is related15:41
Odd_BlokeOh, my thing definitely isn't related.15:54
Odd_BlokeJust annoyed at lxd. ¬.¬15:54
chillysurferhey, all! we're planning on a 19.4 release, is that correct? or did i dream that up? :)16:09
blackboxswnice reproducer Odd_Bloke16:10
blackboxswchillysurfer: correct. trying to get code landed for 19.416:10
blackboxswtrying to wrap up the SRU testing for Ubuntu, but we've hit an lxc problem causing some issues with testing :/16:11
blackboxswchillysurfer: any code that we want explicitly to get in for 19.4 try to get in shape and reviewed by end of week this week if we can16:12
smoserblackboxsw, Odd_Bloke . ok, this seems working for me.16:13
smoser https://github.com/cloud-init/qa-scripts/pull/13/files16:13
chillysurferblackboxsw: awesome thanks!!16:14
Odd_Blokesmoser: Nice!16:14
Odd_BlokeWill take a look post-standup.16:14
chillysurferi was asking more for the recent pr that was opened up on our side16:14
chillysurferwe'll try to get that pushed through16:15
smoserand also https://github.com/cloud-init/qa-scripts/pull/1216:15
smosersomene (probalby not me) put 'set -x' in16:15
blackboxswsmoser: nice, testing now16:15
blackboxswhrm, still seeing bogus uid /gid even despite having smoser's     lxc(['file', 'push', '--mode=0755', '--uid=0', '--gid=0', '-',16:26
blackboxswon xenial -> eoan lxc launched proposed images16:26
blackboxswresults in no network connectivity16:27
blackboxswand inability to ssh-import-id etc.16:27
rharpersmoser: thanks!16:40
Odd_BlokeYep, I'm also not seeing that as a fix, unfortunately.16:41
Odd_BlokeI'm still seeing ~everything owned by 1000000.16:43
rharperthere's some mention of using snap restart lxd after updating lxd  ...16:46
blackboxswyeah something more critical to lxc/d behavior has changed. Trying to reproduce outside of our tooling16:46
rharperit also restarts all containers as well16:46
* blackboxsw ran snap restart lxd and tried again with same invalid 1000000 uid/guid on most files in /16:55
blackboxswso lxc-proposed-shapshot runs lxc-pstart which on a 'stopped' container I get errors https://pastebin.canonical.com/p/m4jbw8jxf2/17:03
blackboxswor for everyone to see :) https://pastebin.ubuntu.com/p/mYYqrMNxVK/17:03
rharperblackboxsw: you can't run it manually like that17:03
blackboxswrharper: doesn't lxc-proposed-snapshot run in manually17:04
* blackboxsw re-reads17:04
rharperthe snapshot tool creates a temporary profile for a container which makes some config changes to set the init binary before running17:04
rharpertl;dr;  we inject a custom init so we can run stuff inside the container before it is booted with the default init of the system17:04
rharperand then we clean it up17:05
blackboxswrharper: I was trying to do that via https://github.com/cloud-init/qa-scripts/blob/master/scripts/lxc-proposed-snapshot#L124-L13117:05
blackboxswlxc init ,, then use lxc-pstart (which is what $cmd is there)17:05
rharpersure, did you set up the profile and modify the container config ?17:05
rharperat this point, I Don't think we're writing files with the incorrect uid/gid17:06
rharperI believe it's getting mapped wrong or possibly the publish is at fault17:06
blackboxsw+1 rharper we aren't writing them. I just wanted to get back to simple lxc cmds that reproduce it17:06
blackboxswyeah agreed17:06
rharperthat said, I'd like to post-pone any poking on this post-sru verification17:06
rharperit's a timesink for now; and we can debug after verification17:07
blackboxswyeah I suppose we can just validate pre-upgrade & post-upgrade on a running contaianer17:07
blackboxswfor most of the 1offs17:07
Odd_Blokeblackboxsw: We can also run containers in a bionic VM.17:08
blackboxswgood point, will do17:14
chillysurferis there a way to prevent Platform.destroy from being called in cloud-tests? i specify --preserve-instance but that seems to not stop the platform from being destroyed17:20
MrGeneralHowdy guys. I've installed Debian 9, and then cloud-init manually (this is for proxmox), though it's not changing anything at all, it's like if cloud-init wasn't installed... Any idea?17:25
smoserrharper, blackboxsw or Odd_Bloke one more psuedo-init fix17:25
smoser https://github.com/smoser/qa-scripts/pull/new/fix/clean-shutdown17:25
powersjchillysurfer, what platform?17:25
MrGeneralam I perhaps missing the cfg file or something I need to edit? Should resize, change the root pw, setup networking, etc.17:25
powersjMrGeneral, have you looked at the cloud-init logs in /var/log17:31
MrGeneralnope, as I create the template, does the VM have it? hum, I'll check17:31
MrGeneralthough I mounted it in Proxmox, IDE17:31
MrGeneralisn't it needed to mount in proxmox?17:31
chillysurferpowersj: azure17:33
chillysurferpowersj: i see the reference to AzureCloudPlatform.destroy but it doesn't seem like anything in azurecloud is calling that particular method17:34
blackboxswMrGeneral: whether cloud-init is run or not depends on cloud init generator adding systemd units/services to the boot goals. If those cloud-init* stages are not included in boot goals (or if there was a systemd dependency chain that was in conflict, cloud-init services may not have been started on that boot.17:35
MrGeneralhmhm got it, I'll give ita try17:35
blackboxswcould check for systemd Breaking ordering cycle by deleting job logs in /var/log/syslog17:35
blackboxswour maybe journalctl17:35
MrGeneralhmhm definitely will try17:36
blackboxswprobably could add that debug info to https://cloudinit.readthedocs.io/en/latest/topics/faq.html for common questions/debugging why cloud-init doesn't start17:37
MrGeneralI'll thank you :)17:38
MrGeneral*I'll check thank you17:38
MrGeneralHumm @blackboxsw, it looks like it's not reading the cloud-init image as per https://pve.proxmox.com/wiki/Cloud-Init_Support ( The next step is to configure a CDROM drive which will be used to pass the Cloud-Init data to the VM.17:56
MrGeneralqm set 9000 --ide2 local-lvm:cloudinit)17:56
MrGeneralit should though...17:56
MrGeneralAny hint?17:56
blackboxswnot sure MrGeneral, haven't used proxmox :/  but if you can access  the running vm somehow. try running DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force   # to see what ds-identify thinks it detects are your datasource18:13
powersjblackboxsw, Odd_Bloke rharper where did you all get with lxc?18:17
MrGeneralWeird, @blackboxsw basically proxmox mounts cloud-init, and reats the meta from there, no idea what's going on :\18:30
MrGeneralbash: /usr/lib/cloud-init/ds-identify: No such file or directory , nope :\18:31
MrGeneralThat's the issue...18:32
MrGenerale.g debian 10 works fine, as centos 7, these read from the mounted ide218:33
MrGeneralSo this HAS to be the issue...18:33
MrGeneralAny idea tho? :|18:33
MrGeneralhttps://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html / You can provide meta-data and user-data to a local vm boot via files on a vfat or iso9660 filesystem. The filesystem volume label must be cidata or CIDATA.18:33
MrGeneralshould be this, dunno18:34
MrGeneralcdrom contains that, on same iso encoding18:34
MrGeneralor OpenNebula..18:35
chillysurferpowersj: yeah looking at the logging, --preserve-instance keeps the vm running but then it turns around and destroys the resource group which then of course deletes the vm as well18:35
MrGeneralBasically https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html I need to enable this. Heh.18:40
MrGeneralIssue seems to be activating nocloud @blackboxsw and I need to have it load the meta-data from cdrom.18:47
MrGeneralThat is the issue.18:47
powersjMrGeneral, not sure many of us are hugely familiar with proxmox, but have you tried going through https://pve.proxmox.com/wiki/Cloud-Init_Support18:48
MrGeneralyep definitely have.18:49
MrGeneraljust cant get cloud-init to load the meta-data from the cdrom18:49
MrGeneralthanks btw powersj18:49
MrGeneralchecking a working instance now, as centos7 works perfectly well18:50
powersjMrGeneral, ok and were you able to run cloud-id. I know the file it produces wasn't there, but did you try running it18:51
MrGenerallet me check sec.18:53
rharperpowersj: we're avoiding the issue for now but using bionic VMs to create containers19:11
* meena is gonna write some code…20:03
meenaanyone wanna tell me how why this test is failing: https://travis-ci.org/canonical/cloud-init/jobs/623839861#L279-L29520:11
Odd_BlokeMrGeneral: Debian 9 is oldstable, right?  The version of cloud-init there is very old, so you may want to try a more recent version.20:17
Odd_Blokemeena: So that failure is telling you that m_user.call_args_list is empty instead of containing the two calls you expect.20:22
Odd_BlokeIf you're pretty sure the code under test is correct, the most likely issue is the mocking.20:22
chillysurferanybody seen this error when trying to build deb with lxd for running cloud-tests? `FileNotFoundError: [Errno 2] No such file or directory: 'ud'`20:23
chillysurferunit tests pass when i run locally but seems to be a problem building the deb in an lxd container20:23
Odd_Blokechillysurfer: Could you pastebin a bit more context?20:24
Odd_Blokemeena: You could also check if _user or _group are getting called, which might suggest that you aren't going down the FreeBSD path properly.20:24
chillysurferOdd_Bloke: https://gist.github.com/trstringer/9ebb45558934f007a2d8af4fde56035020:26
meenaOdd_Bloke: oh. i didn't think of that.20:27
chillysurferOdd_Bloke: specifically: https://gist.github.com/trstringer/9ebb45558934f007a2d8af4fde560350#file-output-log-L263020:27
chillysurferi think ud is the userdata file but not sure why this would fail with lxd but not locally20:27
Odd_Blokechillysurfer: Is this a clean git tree?  (master?)20:29
chillysurferOdd_Bloke: it's pretty much just a single unrelated commit on top of master: https://github.com/trstringer/cloud-init/tree/thstring/fix-azure-cloud-tests20:30
chillysurferi needed to make that commit to even get this far. without passing userdata it was bombing out20:30
chillysurferOdd_Bloke: i could try passing in some user data to the test, but that seems unnecessary. how do you pass userdata to citest?20:31
Odd_BlokeYeah, that doesn't _look_ like it shold be the issue.20:31
chillysurferOdd_Bloke: agreed20:31
chillysurferbut i can't repro it locally20:31
Odd_Blokechillysurfer: So the failure you're seeing is during the package build that the cloud_tests perform.20:31
meenaOdd_Bloke: it is, indeed called.20:31
chillysurferOdd_Bloke: correct20:31
Odd_BlokeSo passing something into citest wouldn't get you anywhere, those are just the regular unit tests failing for some reason.20:31
chillysurferOdd_Bloke: ah right. duh20:32
chillysurferOdd_Bloke: for what it's worth, i initalized lxd with `lxd init --auto`20:33
chillysurfermaybe that's a bad lxd initialization for this build?20:33
Odd_BlokeThat's also unlikely to be it.20:33
chillysurferthought so20:33
chillysurferbut i'm surely not the first person/computer running a build in lxd from master..?20:34
chillysurfermaybe it's environmental20:34
blackboxswrharper: and Odd_Bloke error hit on oracle SRU (not a regression) https://pastebin.ubuntu.com/p/MrC2Hd62gz/20:34
rharperblackboxsw: on xenial ?20:34
blackboxswin the above, I think we might be able to handle/avoid this error in OpenstackLocal ds detection20:34
Odd_Blokeblackboxsw: Is that new?20:34
blackboxswOdd_Bloke: not new at all20:34
blackboxswit was in prevous SRUs too20:34
rharperI see that on xenial if you attempt to re-run local with networking still up20:35
blackboxswjust something we could improve (even though oracle shouldn't be on openstack datasourcE_list in the future20:35
rharperie, if you reboot, it works as expected;20:35
blackboxswrharper: that's due to ephemeraldhcp setup20:35
Odd_Blokechillysurfer: What's the full command line you ran to kick the tests off?20:35
rharperI've only seen that if the ephemeral runs while networking is already up20:35
rharperblackboxsw: well, you shouldn't normally see it20:35
rharperduring boots20:35
rharperwhich I'm not20:35
rharperso how are you seeing it ?20:35
blackboxswon oracle's case, I think normally we shouldn't see that20:35
rharperI don't think we should see that _anywhere* via normal boots20:36
rharperso interested in how you saw it20:36
chillysurferOdd_Bloke: tox -e citest -- tree_run --verbose --data-dir results --preserve-data --platform azurecloud --os-name bionic --preserve-instance --test modules/write_files20:36
blackboxswrharper: I actually see it on initial boot on oracle. I'll double check now20:36
rharperplease do20:36
blackboxswintiial boot (not upgraded to proposed)20:36
Odd_Blokechillysurfer: So a short-term workaround would be to build your own deb and pass that in.20:36
blackboxswwill ping with results20:36
rharperof which release ?20:36
blackboxswxenial and bionic20:36
chillysurferOdd_Bloke: yep good idea20:36
rharpervery strange20:36
rharperbaremetal ?20:36
chillysurferOdd_Bloke: that *should* work i would hope20:36
blackboxswrharper: not bare metal20:36
blackboxswparavirt I think20:36
rharperon iscsi we're up20:37
rharperon paravirt, this should not happen unless network config is somehow baked into the iamge20:37
Odd_Blokerharper: blackboxsw: If this isn't new, let's file a bug and move on.20:37
rharperOdd_Bloke: +1 but let's confirm it's not new20:37
blackboxswRemote Data Volume:20:37
blackboxswBoot Volume Type:20:37
blackboxswyeah wil lconfirm it's not new. and will file a bug20:37
rharpersmells wrong to me20:37
Odd_Blokerharper: I thought blackboxsw did confirm it wasn't new.20:37
rharperwell, he said he saw it before20:38
Odd_BlokeBy all means if we aren't sure, let's make sure we are. :)20:38
rharperbut then somehow we didn't file a bug20:38
rharperso lets do that20:38
blackboxswI think it was on first boot, but will double check20:38
powersjOdd_Bloke, chillysurfer I can reproduce the test escapes in a fresh bionic lxc of master20:38
blackboxswrharper: Odd_Bloke right, on sru 19.2.36 we had two tracebacks (not triaged in the logs) on oracle but I recall we spot checked that and found the same latest/metadata 404 route traces (which is why oracle has their own datasource now anyway instead of using openstack20:40
blackboxswI'm awaiting a clean vm launch now to confirm20:40
rharperblackboxsw: ok, so lets file a bug with the details;  it seems fixable20:41
Odd_BlokeRight, yeah, that's it.20:41
Odd_BlokeThis doesn't happen in the Oracle DS, and the expectation was that we would be moving Soon.20:41
blackboxswright it's a logical path that shouldn't be in use shortly anyway. As long as we confirm as well that Openstack works without hitting this ephemeraldhcp trace, because the platform behaves differenty. This is a no fix needed.20:42
blackboxswwhich I think rharper already confirmed (no traces on openstack SRU testing)20:42
blackboxswrharper: Odd_Bloke confirmed, existing oracle on 19.2.36 has this same issue20:43
rharperblackboxsw: ack, no traces on OpenStack20:43
blackboxswon clean boot20:43
blackboxswultimately the proper OpenStack ds is detected (just not OpenstackLocal)20:43
blackboxswso we just detect a little later in the process. And we're working on CPC images to not default datasource_list: [Openstack] anyway on xenial++ I thought.20:44
* blackboxsw looks the other way. "Nothing to see here'20:44
blackboxswhttps://github.com/cloud-init/ubuntu-sru/pull/71 softlayer SRU20:47
blackboxswhttps://github.com/cloud-init/ubuntu-sru/pull/66 azure SRU20:47
blackboxswhttps://github.com/cloud-init/ubuntu-sru/pull/74 oracle SRU20:48
blackboxswhttps://github.com/cloud-init/ubuntu-sru/pull/74 ignore ssh pub keys20:48
meenaoh hmmm…20:52
* blackboxsw wraps up puppet SRU verification test now20:55
Odd_Blokeblackboxsw: Comment on #73.20:59
blackboxswthanks Odd_Bloke responded and force-pushed21:04
Odd_Blokeblackboxsw: A suggestion added. :)21:16
blackboxswand accepted21:16
smoserso did my pstart stuff fix the issue ?21:18
smoser(i didn't actually *see* an issue, i just responded to blackboxsw's totally rude suggestion that we should drop some code i offered)21:18
blackboxswsorry smoser, I was wondering if the pstart approach was giving us flak as an unsupported lxc init use-case21:19
blackboxswwe were going to talk about this post-SRU. so probably tomorrow  to dig into the lxd issue being caused, but I'll run through your additional patches and see if we can't fix what lxc/lxd 3.18  broke21:20
blackboxswsmoser: at the moment, I'm running lxd related proposed tests on a bionic kvm and things are working as they used to21:21
blackboxswsomething w/ focal + lxd snap21:21
meenahow do i start a debugger on the failing tests?21:21
blackboxswmeena: unit tests add an import pdb; pdb.set_trace() and run .tox/py3/bin/nosetests tests/unittests/.....your file21:21
Odd_Blokesmoser: The first patch didn't fix it for me, unfortunately.21:22
blackboxswmeena: unit tests add an import pdb; pdb.set_trace() and run .tox/py3/bin/nosetests tests/unittests/.....your file   -s21:22
Odd_BlokeHaven't tried since.21:22
blackboxswsmoser: same with the first two patches you suggested (hadn't tried the third yet)21:22
smoserOdd_Bloke: is there a url that shows failure?21:23
smoseror can you paste it or something ?21:23
smoserat least 'lxc-proposed-snapshot disco test-d1' worked.21:23
Odd_Blokesmoser: Including launching a container from the produced image?21:25
smoseri'll give it a try.21:26
blackboxswsmoser: I can run this           lxc-proposed-snapshot -p disco test-d1;  lxc launch <fingerprint> test; lxc exec test -- ls -l  and I see21:26
blackboxswdrwxr-xr-x   1 1000000 1000000  102 Dec  4 03:04 usr21:26
blackboxswdidn't actually get any error logs on snapshot creation21:27
* blackboxsw wonders if it has something to do with lxc now publishing cloudimages that are squashfs/metadata instead of parts and us using a unified tarball for image snapshot upload21:32
blackboxsws/instead of parts/in separate file parts/21:33
smoserthis is really messed up21:33
meenawhat do i have to do to get a newly pip installed package importeded, or importable…21:34
meenahttps://documen.tician.de/pudb/starting.html ← installed this debugger, which sucks slightly less than pdb21:34
meenaalso, i enjoy the nostalgia of things looking like Turbo C21:34
blackboxswmeena: if you are talking about adding it the the current tox env, I think you can .tox/py3/bin/pip3 install X21:35
blackboxswand test whether importable via .tox/py3/bin/python3   import X21:35
Odd_Blokesmoser: I take it that means you reproduced? :p21:38
blackboxswsmoser: merged your PR 14 on qa-scripts.  retested again and still not-WFM21:39
Odd_Blokelxd has been using split images forever.21:39
blackboxswOdd_Bloke: right, so this would have hit us last SRU21:39
blackboxswor earlier21:39
smoseryeah. it does not work, blackboxsw21:39
smoserbut it is really wierd what is going on there.21:39
smoserso the easiest way to quickly find out information21:39
smoseris to edit psuedo-init21:39
smoser then run 'lxc-pstart -v -v -v $NAME /bin/bash'21:40
Odd_BlokeI haven't used pudb, but am a big fan of ipdb.21:40
smoserthen sudo cat /var/snap/lxd/common/lxd/logs/d1/console.log21:40
blackboxsw+1 smoser I'll play around with that -> relocating to coffee shop21:40
Odd_Blokeblackboxsw: What happened to looking at it post-SRU? :p21:42
rharperclosed no response. bummer21:45
rharpersame error as your paste smoser21:45
smoserso... if you muck around with pstart, you can get in to that failed case21:47
smoserand look around21:47
smoser(just coment out the 'mount') that is what was fialing for me21:47
smoserand then i can run  /bin/bash21:47
smoserand look... nothing obvious21:47
smosermount is foobarred21:47
smoserroot@d1:~# ls -l `which mount`21:48
smoser-rwsr-xr-x 1 1000000 1000000 47184 Aug 22 23:40 /usr/bin/mount21:48
smoserso yeah, perms are getting not set bakc21:48
smosershiftfs bug ?21:48
smoseror whatever is doing the filesystem uid shift is foobarred21:48
smoserand not changin stuff.21:48
rharperoh they hijack mount now21:49
rharperso help auto mount some things IIRC21:49
Odd_Blokeblackboxsw: Found a potential issue with https://github.com/cloud-init/ubuntu-sru/pull/71/files so I haven't reviewed further21:50
blackboxswthanks Odd_Bloke I'll kick it again with the proper wait logic as we could have missed a trace message21:56
meenayeah; so, i can enter the debugger, step thru the code, and still have no idea why the wrong method is called. maybe something is wrongly mocked22:03
Odd_Blokemeena: So one thing I sometimes do is to get the debugger into the code under test and then start poking around to see what values things have.22:05
Odd_BlokeSometimes you discover that the thing you want _is_ mocked somehow, but not in the way that the test code is written for.22:06
meenaOdd_Bloke: it's all mocked, that's for sure, the question is just, why is the wrong (mock) function called?22:08
Odd_Blokemeena: Poking at the mocked function can help you understand what the incorrect mocking may be.22:09
meenawe created a cloud with a distro freebsd, and a ds DataSourceNone, and then we run the the handler function of the cc_users_groups module. aaand, i have no idea which function is called in the mock.22:10
meenaand why it's the wrong one :O or if i even have my mocks setup correctly hmmmmm22:11
meenaso, is this correct? https://github.com/canonical/cloud-init/pull/93/files#diff-f957401b91b90e8385085395fe1f3623R51 ← are the class mocks passed first, or the method mocks?22:11
meenahow do i ask the mock object, which *fully qualified* function it refers to?22:12
Odd_Blokemeena: An easier way of checking would be to change the order of the two method decorators.22:14
Odd_BlokeBut not the names.22:15
Odd_BlokeThen one of _user and m_user will point at .create_group, and that should answer your question.22:15
Odd_Blokepowersj: Your three man page PRs are Approved now, will leave it to you to squash merge. :)22:17
powersjOdd_Bloke, will do thanks!22:17
chillysurferhow do cloud-tests ssh into the cloud machines? is it straightforward what key is used and the user name? need to troubleshoot a platform machine that is being tested that apparently cloud-tests can't ssh into, but it seems up and running22:18
meenaOdd_Bloke: where do you get these good ideas from?22:19
meenaOdd_Bloke: still, i'd like to be able to tell from the mock object what the fully qualified name is… this is… painful.22:21
meenagreat, fixed test: https://github.com/canonical/cloud-init/pull/93 pls merge :P22:25
rharperchillysurfer: I believe in the results dir the artifacts include the ssh key pair22:25
rharperchillysurfer: in the topdir of results, there should be a cloud_init_rsa/cloud_init_rsa.pub set of files22:26
chillysurferrharper: oh nice22:36
chillysurferrharper: and it's user `ubuntu` is that right?22:36
powersjchillysurfer, for azure it should be ubuntu, I think for lxd we still use root22:39
rharperchillysurfer: for ubuntu images at least22:42
powersjmeena, for FreeBSD can you review https://github.com/canonical/cloud-init/pull/93 just to give it a +123:09
meenapowersj: i just wrote that code23:11
powersjdoh, so you are igalic on github?23:11
meenapowersj: i am @igalic23:11
blackboxswman softlayer really taking 3 mins to spin up an instance?23:11
meenagithub won't allow me to approve my code23:12
powersjyeah... ok I'll have someone else review23:12
meenapowersj: did i not link the horrible man page?23:13
powersjah ok I just need someone to review the tests and we should be g2g23:16
meenavs https://www.freebsd.org/cgi/man.cgi?pw#USER_OPTIONS s ee description of -h23:18
meenahttps://github.com/canonical/cloud-init/pull/53 has anyone seen rharper around?23:20
meenahttps://github.com/canonical/cloud-init/pull/42 cuz, there's some stuff i'd really like rharper to look at23:22

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