[00:00] axw: PTAL http://reviews.vapour.ws/r/1373/ (should be quick) [00:02] anyone familiar with upgrades, willing to answer a couple questions? [00:05] ericsnow: done [00:05] * axw goes for breakfast [00:05] axw: thanks! [01:13] wallyworld: can you please link me the status spec? [01:13] axw: https://docs.google.com/a/canonical.com/document/d/1SsHDxi58xgrim6VTKorqMn4GlzxPV9EFvu1ueBgnMlc [01:13] ta [01:17] wallyworld: so, a charm can never status-set error. what if the software is irreparably broken? [01:18] i.e. the charmed service, not the charm itself [01:18] axw: it then sets blocked [01:18] blocked means it can't run and a user has to intervene [01:18] for whatever reason [01:18] error is reserved to report hook errors only [01:19] wallyworld: mk. that implies to me that it can be repaired, which may be optimistic [01:19] * axw continues [01:23] axw: wrt storage add, did we want the additional storage (eg a new volme) to be able to get different sizing, tags etc, or did we want to enforce storage add must create the new volume exactly the same as the first one [01:24] wallyworld: I think it should take the same args as "--storage" in "juju deploy" [01:24] wallyworld: i.e. pool,size,count [01:24] axw: awesome, that was my tpught also [01:24] just wanted to confirm [01:25] ty [01:25] np [01:45] can I get one more set of eyes on http://reviews.vapour.ws/r/1371/ === natefinch-dinner is now known as natefinch [02:02] wallyworld: reviewed [02:02] axw: ty, will look [02:02] wwitzel3: will take a look soon [02:04] axw: thanks, appreciate it [02:04] axw: my stuff needs to be in for 1.23 that is getting cut basically ASAP... so if you could prioritize it, I could get it merged (barring major problems, of course) - http://reviews.vapour.ws/r/1299/ [02:04] natefinch: ok [02:05] axw: thanks, I appreciate the help. === ericsnow is now known as ericsnow_afk === ericsnow_afk is now known as ericsnow [02:47] axw: i've updated the pr for that health branch, after you finished your current review [02:47] wallyworld: ok [03:14] axw: i have to go out for lunch, if when you look at the pr you are happy with it, could you $$merge$$ for me and i'll propose the next one when i get back [03:15] wallyworld: np [03:15] ty === ericsnow is now known as ericsnow_afk === ericsnow_afk is now known as ericsnow [03:48] wwitzel3: reviewed, sorry for the delay [03:49] axw: np, thank you [03:51] axw: it requires work, so I won't get to it until tomorrow anyway ;) [03:51] wwitzel3: sorry :~( [03:52] * axw is creating work for lots of people today [03:52] haha [03:52] that's probably a good thing [05:00] okay, 1.23-beta2 has been really flaky with local provider [05:00] seems about every third machine doesnt' get the agent running on it [05:05] I realize that's not helpful, I'm gathering log files [05:12] re-ran cloud-init, I think this is a problem with the seed data, ssh keys aren't getting installed [05:23] I also can't seem to connect to the API with python-jujuclient anymore. I noticed that the api server is only listening on ipv6 [05:23] is this a new configuration? [05:26] prefer-ipv6: false is in my jenv, not sure why the api-server is only binding to the ipv6 address locally, this may be a redherring [05:26] also noticed that the user changed to admin where it was user-admin previously [05:52] wallyworld: if you can take a look at http://reviews.vapour.ws/r/1360/ and http://reviews.vapour.ws/r/1361/ some time today, I'd be most grateful [05:52] sure, np. thanks for landing my stuff [05:52] i'm just doing a pr for the next bit [05:52] wallyworld: nps [05:52] cool, ping me and I'll review [05:54] axw: http://reviews.vapour.ws/r/1376/ [05:54] looking [05:55] ah i half looked at the managed filesystem source one last night, looked good [05:58] wallyworld, Would you have time to read over bug 1435644, or suggest someone? It's a private cloud streams question and I know you've been able to give guidance on similar bugs. [05:58] Bug #1435644: private cloud:( environment is openstack )index file has no data for cloud [05:58] jog: ok, sre [05:59] wallyworld, thank you, it needs another set of eyes, as I'm not sure what to suggest. [06:00] jog: i just need to finish a few things, will comment on the bug when i can [06:01] wallyworld, np I'm EOD [06:01] ok [06:05] axw: http://reviews.vapour.ws/r/1377/ can you give it a quick look? It is the same patch as katco but it just fixes a test that was also using the leader-election feature flag (which is now removed) [06:05] jam: okey dokey [06:05] thx [06:05] hmmm... I think it is supposed to be targetting 1.23 I'll have to check on that [06:08] jam: shipit [06:08] ah yeah, probably [06:08] axw: I have to rebase it, but I'll propose another one for 1.23 [06:09] jam: nps, I expect it'll be exactly the same given the size :) just merge if so [06:09] axw: sgtm [06:29] where does juju cache it's api endpoints? [06:30] axw: so it looks to be an entirely bigger patch. I have the feeling master is not up-to-date with the leader-election code that is in 1.23 [06:30] I changed values in the api endpoints in .jenv but it says loading from cache [06:31] tbh I was surprised the patch was so small [06:31] the flag in master only changes the client side (essentially), but all of the internal workers were running behind that flag in the 1.23 branch. [06:34] jam: as was I. I'll take a look [06:35] katco: ping [06:37] jam: LGTM [06:37] what is the api user in juju? user-admin or admin? [06:37] axw: http://reviews.vapour.ws/r/1378/ is the newer proposal, but I'm running through tests, etc since it kept growing. [06:38] sure [06:38] marcoceppi_: the name of the user is "admin" the *tag* is "user-admin" (vs machine-0 etc) [06:38] jam: so what should I use in the websocket? user-admin? [06:40] marcoceppi_: so in most of the API we talk in terms of tags. so Login probably wants 'user-admin', but know that in the future we're looking to be able to name those users and they will then be "user-joe" etc. [06:40] I believe the agents login as "machine-0" etc. [06:40] sure, thanks [06:41] I'm having a hell of a time getting python-jujuclient to connect to 1.23-beta2 bootstrapped environment [06:42] wallyworld: reviewed [06:42] ty [06:42] marcoceppi_: I believe thumper has been making changes to Login which is supposed to be compatible, but I thought he had to submit some patches recently. [06:43] let me try rolling back to 1.22 [06:44] marcoceppi_: if something is broken wrt compatibility, we really appreciate that feedback [06:44] well, *I* appreciate it, hopefully the people who have to fix it do too :) [06:44] jam: I need to do more testing, I'm having a hard time locking this down [06:44] other than "it's not working" [06:45] marcoceppi_: sure. if it doesn't "just work" and it used to, then we certainly have a bug [06:45] too many moving pieces [06:45] wallyworld: BTW, I saw later that the time is set by the state server. you can probably safely ignore my comment, I was just thinking it would be nice to show relative times in the UI [06:45] wallyworld: but that involves quite a bit of complexity, in order to ensure timestamps are synchronised between state servers and clients [06:46] axw: Agreed, this is one area where I'm hoping for feedback from users. The spec says timestamp but I suspect we'll be asked for relative times instead/as well as. [06:46] i just want to get *something* reasonable out there so we can then see what real users ask for and complain about [06:46] * axw nods [06:49] wallyworld: axw: you probably need to use the universal "time since epoch GMT" timestamp, and then on the client turn that into localtimes. It seems the most portable way [06:49] relative times (as in 1hr ago) seem like a fair amount more work. [06:50] jam: it does store epoch [06:50] on client it formats as RFC822 [06:50] jam: that still assumes the clocks are all correct. I suppose it's fair to say that if they're not, you're on your own [06:50] i can't recall if that includes tz conversion [06:50] axw: if you're clocks aren't reasonably close to reality there isn't really much we can do is there? [06:50] wallyworld: it just displays the timezone it's in. you could concert to local TZ [06:51] ah, i did mean to do that, but it got late [06:51] jam: well, you can implement poor-man's NTP, but it's probably not worthwhile :) [06:51] jam: okay, there's an issue in 1.23-beta2 [06:51] axw: i am counting on our deployents using NTP OOTB [06:52] marcoceppi_: a bug is appreciated, targetting the 1.23 series, as this seems pretty critical. It *might* already be fixed but I wouldn't hold my breath on it. [06:52] jam: just writing repro steps [06:52] jam: would it be worth compiling the 1.23 branch of the repo to verify as well? [06:52] jam: in my former life, I worked on a distributed system where the servers (owned by customers) were *constantly* skewed and they would never run NTP. I think it's okay to rely on NTP, I just had flashback nightmares [06:52] wallyworld: SGTM [06:52] axw: :) [06:53] marcoceppi_: if you want to take the time, its nice to have the info, but its mostly a "do what you can" sort of thing. [06:53] it's not your responsibility to fix all our bugs, but we're happy to have your support [06:53] it's 3am and this has blocked me, I don't have much else to do [06:56] I'm sorry to hear that, and sorry that we broke stuff, but certainly appreciate you discovering it. [06:56] much better to find out in a beta release. [07:00] jam: http://pad.lv/1439535 [07:00] I'll try compiling 1.23 from github then try trunk as well [07:04] morning all [07:04] marcoceppi_: thanks for investigating, that looks much weirder than I expected [07:09] jam: fwiw, this works with 1.23 branch (juju version shows 1.23-beta3) [07:09] Bug #1439535 was opened: 1.23-beta2 websocket incompatibility

[07:09] voidspace, morning [07:10] voidspace, there's a new bug about the addresser I've assigned to you [07:11] voidspace, trivial to fix - just don't start the worker if environs.SupportsNetworking() returns false [07:12] dimitern: ah, ok [07:12] dimitern: easy enough :-) [07:13] dimitern: is it a problem to have an addresser around otherwise? [07:13] voidspace, well, I don't think so - but it should not spam the logs and restart every 3 seconds :) [07:14] dimitern: ah, yes it is a problem [07:14] dimitern: just reading the bug :-) [07:14] voidspace, I'd prefer to have it running in all environments TBH [07:15] voidspace, but without a netEnviron interface it can't do its job anyway [07:15] marcoceppi_: I don't see anything specifically in "git log --first-parent juju-1.23-beta2..1.23" that makes it clear why your API issues would have been fixed [07:16] marcoceppi_: is this local provider? [07:16] yeah "switch local" [07:16] jam: aye, it is [07:17] axw: i'm going blind, i can't see what calls func processPending(...) [07:17] wallyworld: the main loop in storageprovisioner.go [07:17] at the top [07:17] marcoceppi_: which makes me worry that it is more of a packaging issue. [07:17] dimitern: voidspace: do you know if the backport of "addressable containers" into 1.23 would have affected local provider? [07:18] jam: really? seems odd it would be in packaging [07:18] marcoceppi_: to quote sherlock holmes, "when you have eliminated the impossible, whatever remains, however improbable, must be the truth?" [07:18] marcoceppi_: I certainly wouldn't expect it there either. [07:18] jam, it's not a backport - it was first implemented in 1.23, but it shouldn't affect the local provider [07:19] dimitern: I just see addressing changes in 1.23 beta 3 [07:19] which *could* be something that would allow local provider to work/not work. [07:19] marcoceppi_: I don't see anything about login, etc changing [07:19] wallyworld: found it? [07:19] axw: ffs, looked straight past it. the process functions aren't thread safe, is it worth a comment that they're being called from a single threaded loop, or is that asking for an unnecessary comment [07:19] marcoceppi_: just to eliminate variables, can you "git co juju-1.23-beta2" and see if it is broken for you ? [07:19] jam, it's possible, however the local provider does not use the same brokers as other providers, where most of the changes are [07:20] wallyworld: like the uniter, the whole thing is not goroutine-safe [07:20] jam: sure [07:20] wallyworld: I can put a comment, but I'm not sure where it'd go ... [07:20] fair enough [07:20] I see changes to GCE, but those should also not effect local [07:20] don't wory [07:22] marcoceppi_: I do see a change to how local provider was getting its IP address. I wonder if it was suffering from the "claim I'm on the LXC bri [07:23] bridge bug in 1.23-beta2" [07:23] jam: possibly? about to compile [07:25] axw: reviewed, just a few small comments/suggestions [07:25] wallyworld: cheers [07:25] anyone have thoughts on expired cert issues? [07:26] 1.23 points to go.googlesource.com [07:26] which has a bad cert [07:26] yup, I give up jam, 1.23-beta2 from source works [07:27] nm. I was testing in a VM that had been suspended for 2 weeks, and the time hadn't updated yet. [07:27] so their cert was renewed 2 weeks ago [07:28] marcoceppi_: le sigh.... [07:28] marcoceppi_: but you can reliably reproduce when running /usr/bin/juju, right? [07:28] jam: another fix that went in into 1.23 related to http- and apt- addresses that may affect marcoceppi_ is the check for loopback address [07:28] jam: everytime, going to spin up another vm to verify [07:28] anastasiamac: yeah, but in theory he just tested rolling back his local build to 1.23-beta2 and it still passed [07:28] jam: however m not sure why there would b a diff btw 1.23-beta2 and 1.23-beta3 with respect to this fix.. [07:29] jam: yep.. [07:29] marcoceppi_: the other thing is to make sure you do "godeps" and all that, just in case there is some depedency we were using in 1.23-beta2 that had something wrong. [07:29] jam: I run godeps everytime I build [07:29] following this workflow: http://marcoceppi.com/2014/11/compiling-juju-core-from-source/ [07:30] marcoceppi_: that looks decent to me [07:30] having various versions of juju in $PATH could confuse things in the past, did you check if there were build errors? [07:31] (as that would leave the other 1.23 around in $GOPATH/bin) [07:31] axw: can you try a quick test for me? "cd worker/uniter; go test -check.v -check.f Leader" [07:32] I'm still sorting out things in this VM, but on other machines it was failing for me. I'm wondering if the tests are just poorly isolated (they use some other test's setup to be able to work properly) [07:32] or maybe I'm just insane :) [07:32] jam: juju version reported 1.23-beta2 and `which juju` was the one in $GOPATH/bin [07:33] marcoceppi_: were you running "juju foo" or $GOPATH/bin/juju foo ? [07:33] IIRC, there was a really old bug at one point where because juju was running sudo [07:33] just `juju foo` [07:33] it would find the wrong juju because root's PATH was not user's PATH [07:33] I can try again with full path [07:33] marcoceppi_: I don't expect that's the problem, but just trying to eliminate possibilities [07:33] sure [07:37] jam: will do, with your 1.23 branch you mean? [07:37] axw: i'm having it fail on master as well as stock 1.23 [07:38] there it passed [07:38] at least that gives me a baseline [07:38] the VM is happy [07:38] jam: yeah, I'm unable to reproduce on a clean vm now [07:38] jam: works on master for me [07:39] there's something buggered with my setup, this was just a big 'ol snipe hunt [07:40] axw: thanks for confirming. I'll just move forward :) [07:58] dimitern: for bug 1438683 [07:58] Bug #1438683: Containers stuck allocating, interface not up

[07:58] voidspace, yeah? [07:58] dimitern: can you point me to where in the logs or config that indicates eth1 is being used [07:59] dimitern: I can't find eth1 mentioned by name or MAC address like this [07:59] dimitern: and the reference to primary network in the logs is for eth0 [07:59] voidspace, in machine-0.log around returning the result from PrepareContainerInterfaceInfo [07:59] dimitern: ok, thanks [08:00] dimitern: and there it is... [08:00] voidspace, as for eth0 being primary - there are 2 places (also in that log) - before starting but after acquiring the instance, and before starting the container [08:00] dimitern: I grepped for "eth1", not sure how I missed that :-/ [08:00] voidspace, :) [08:02] dimitern: ok, so easy [08:02] dimitern: we iterate over all subnets and map subnets to interfaces [08:02] dimitern: we don't check if the interface is disabled - and where the same subnet appears more than once we'll overwrite [08:02] voidspace, yeah - both of these are problems [08:03] dimitern: so we *do* need to skip disabled interfaces there [08:03] dimitern: that will be the problem [08:03] voidspace, where? [08:03] dimitern: prepareAllocationNetwork [08:03] dimitern: lines 1021 and 1051 [08:04] coffee [08:04] voidspace, so the result of NetworkInterfaces should include all NICs we can find, but with correct device index and disabled flag [08:05] dimitern: yep, I already have a fix for that - although "correct device index" is a bit arbitrary if lshw doesn't give it to us [08:05] dimitern: and when we iterate over interfaces to pick we should be skipping disabled ones [08:06] voidspace, hmm I'm not quite sure [08:06] dimitern: this is in prepareAllocationNetwork I'm talking bout [08:06] *about [08:07] voidspace, even if we skip them, we still shouldn't overwrite the subnet info in case more than one nic is on the same subnet [08:07] dimitern: do we ever want to return interface info for a dsiabled nic? [08:07] dimitern: agreed, but that's a different issue [08:07] although [08:07] we need to pick *an* interface, so if we have picked a subnet and allocated an address on it - we only need one non-disabled nic [08:08] so overwriting isn't really an issue (so long as we skip disabled ones) [08:08] voidspace, if by "return" you mean from NetworkInterfaces() - yes, we want that; in prepareAllocationNetwork though - that's different [08:08] it's prepareAllocationNetwork I'm talking about [08:08] voidspace, ok [08:08] that's where the specific problem is [08:08] dimitern: in prepareAllocationNetwork do we want to always prefer the primary network, unless it's disabled? [08:09] and always try that first (try to allocate an IP on the subnet associated with the primary interface) [08:10] voidspace, just keep in mind that we'll most likely start allocating addresses (and creating NICs) for containers such that we have a 1:1 correspondence with the host enabled nics [08:11] ok [08:11] voidspace, so in the long term it doesn't matter which NIC is primary [08:11] so I don't think overwriting actually matters, as we only want to pick one nic anyway [08:11] but we *do* need to skip disabled networks in prepareAllocationNetwork [08:12] voidspace, but for now we only want 1 address/nic per container - connected to the host's primary nic [08:12] which is a 3 line fix plus test... (along with the device index fix I already have for NetworkInterfaces) [08:12] voidspace, yes, but we shouldn't pass [id1, id1] to Subnets when we have 2 nics on the same subnet id1 [08:13] voidspace, (or if we do, we should only fetch the info once per unique id) [08:13] dimitern: ok, that's also true [08:13] :-) [08:15] :) [08:44] dimitern: so the singular runner doesn't have an obvious way to not start a worker [08:45] voidspace, it won't start it if you don't add it to the list of workers to run :) [08:45] dimitern: right - so in which case the agent needs to construct an environ [08:45] dimitern: *or* we can start the runner and Handle can be a no-op if networking isn't supported [08:46] dimitern: either is fine, I'd just like to know which is preffered [08:47] dimitern: startEnvWorkers (cmd/jujud/agent/machine.go) doesn't currently have an env [08:51] voidspace, I think we should start it [08:52] voidspace, but then internally it should handle "networking not supported" properly, i.e. logging that it won't do anything, but not returning an error [08:53] dimitern: that's fine - and easier :-) [08:55] voidspace, exactly :) [08:58] dimitern: shit, exactly this moment the garage comes to fetch my car. will report afterwards, got an idea after your hint [08:59] TheMue, ok, no worries [09:24] wallyworld: in your email you wrote "juju-get" and "juju-set". I think s/juju/status/ ? [09:42] dimitern: thinking about I would say your theory is correct, I'll talk to rvba. when watching the node during boot and it's wanting to fetch metadata from the controller the return code is 404. === mgz is now known as mgz_ [09:43] dimitern: this sounds like "yes, I can connect the server, but it doesn't has the info (here the lshw) that I want." [09:45] TheMue, yeah, something like this - perhaps it's not because lshw is missing, but something else [09:47] dimitern: maybe, I'll discuss on #maas. but it seem to be able to at least reach the maas controller. and that's why pings also work. [09:48] TheMue, yeah, ok [09:48] btw, my car is now gone *sniff* less than a year old [09:57] dimitern: not sure if it's due to networking stuff going on, but I cannot "juju ssh" to ec2 machines on master. works fine if I disable proxying through machine-0 [09:57] dimitern: I get "nc: getaddrinfo: Name or service not known" [09:58] axw, hmm odd I'll try here with a fresh tip of master [09:58] axw, but it will be in about half an hour [09:58] dimitern: no rush, just thought I'd let you know in case you knew of somethign related [09:59] axw, do you have containers deployed on machine 0 ? [09:59] dimitern: could be unrelated, I see a bunch of network failures due to network resolution failing [09:59] dimitern: nope [10:00] axw, if you paste me some logs I'll investigate [10:00] I just destroyed, I'll recreate [10:15] dimitern: never mind, must've been an intermittent DNS error. [10:36] axw, *whew* good! :) [10:58] * dimitern goes to get his car back [11:01] axw: i was just looking at NewClient in apiserver/client [11:02] axw: ISTM that you could save a mongo round trip in every single API call by using common.NewToolsURLGetter(st.EnvironTag().Id(), st) [11:02] axw: instead of fetching the env from mongo every time [11:03] axw: (unless there's some reason that the env uuid might change, i guess) [11:06] rogpeppe: yeah, agreed. that possibly predates EnvironTag caching... pretty sure that value is fixed [11:07] axw: cool. might be worth bearing in mind. [12:43] axw: *if* you're still around I have a new update for the branch. Unfortunately, we still have 1 test that fails because it is nondeterministic. I haven't figured out how to fix that yet. [12:43] katco: are you around? [12:43] katco: if/when you are, I've been looking at enabling leader-election always in http://reviews.vapour.ws/r/1378/ [12:43] it is almost complete except for one big TODO. If you have time, I'd appreciate a look at it. [12:44] I think we could enable this in production, because the test is failing because we're triggering a hook that should be triggered, but at a random time so I can't just add it to a fixed spot in the test expectation. [12:49] back [13:11] alexisb: I don't have a blessed revision, and there's at least one GCE bug unfixed. Do you want to meet anyway? [13:12] alexisb: Correction, I see a bless for 16bed49 in build 2508 [13:13] alexisb: Correction 9710c29 / 2509 [13:13] yeah, the ppc tests managed to get through on that one [13:14] mgz: local-deploy-vivid-amd64 was stuck for most of yesterday, and is stuck in the same way today. I am disabling it. [13:21] abentley: fair enough [13:31] dooferlad, voidspace, ping [13:32] I feel like I'm talking to myself >_< [13:32] dimitern: heh [13:32] katco: are you around? I'm trying to test cn and the v4 signing code on 1.23-beta2 is not playing ball with me it seems [13:35] dimitern: howmy I be o service? [13:40] dimiter: btw, I'll file a bug against maas, it seems to fail during cloudinit [13:43] TheMue, ok, that's what it looked like to me [13:43] yeah, to rvba also [13:43] TheMue, but we should still find a way to reproduce and fix that bug [13:44] to repoduce it is no problem, but we cannot fix the booting bug [13:45] we can fix our bug to stop processing, that's what I've done [13:46] now need tests for it === kadams54 is now known as kadams54-away [13:58] marcoceppi_: ping [14:00] ericsnow, wwitzel3, what is the latest on the GCE bugs? [14:02] alexisb: wrapping up (all but 1 merged) [14:03] hazmat: otp [14:04] marcoceppi_: just curious about that issue w/ py juju client and 1.23.. just looked up the bug report and it looks like its already resolved though. [14:06] ericsnow, axw: could I bother you guys with a closer lookthrough of http://reviews.vapour.ws/r/1218/ and, if you're feeling really adventurous, http://reviews.vapour.ws/r/1330/? :D [14:06] aznashwan: sure thing [14:12] I'm is off for now - might be back later [14:16] jam: mgz: BoD [14:16] jam: one of the tests is failing then? [14:19] alexisb: I should have the last patch up in 20 minutes or so [14:21] katco: bod? beginning of day? [14:21] mgz: yep! [14:21] katco: >_< [14:21] mgz: ? [14:22] katco: so, we expect 1.23-beta2 to work in china right? it has all your code in it. [14:22] katco: I get enough silly acronyms from xwwt [14:22] mgz: as much as we can expect untested fixes to work =/ [14:22] lol [14:22] mgz: Keeps you on your toes. ;) [14:23] mgz: we never had a cn north instance to test against for legal reasons [14:24] katco: how should I go about debugging it? I have flipped the debug flag in goamz, and it basically confirms we are using the v4 path (doesn't print the headers, I could also enable that extra dumping in the signing file), but aws complains at me that the access key query param (I presume) is not supplied [14:24] which is non-sensical as that's not how v4 signing works [14:24] I will paste you my junk for your curiousity [14:24] mgz: hmmm... yes ty [14:26] katco: https://pastebin.canonical.com/128882/ [14:26] * katco looking [14:27] I can try flipping the juju code to always using v4 and running it against us-east-1? [14:28] mgz: that might be informative [14:28] will do that, and turn on the signing debug output [14:29] i'm doing some research on that param [14:32] so, the v2 version does all the query params as normal, plus the access key, plus a hashed-with-private-key param [14:32] mgz: right, v4 uses headers primarily [14:33] yup [14:33] mgz: do you know what request was being made? e.g. what api is failing? [14:34] looks like https://github.com/go-amz/amz/blob/v1/ec2/ec2.go#L1080 ? [14:36] katco: DescribeAccountAttributes [14:37] ericsnow: when you get a minute, could you review this: https://github.com/juju/replicaset/pull/1 [14:37] katco: hm, I didn't get more printed from the signing flipping to os.Stdout at the top [14:37] ericsnow: I found another repo that needed updating [14:37] cherylj: yeah [14:37] katco: same issue with us-east-1 [14:37] cherylj: thanks for being so thorough [14:37] mgz: i think that debugging is only for v4 [14:37] cherylj: I need to add a GH webhook for that repo too [14:38] it's using v4 now [14:38] I flipped it in juju [14:38] ericsnow: thanks! I think that will be the last one [14:38] cherylj: did you mean to remove the summary comment that was on line 1 [14:38] ? [14:38] ericsnow: yes, I did for consistency with the other repos. [14:39] ericsnow: I debated it, but figured I should err on the side of consistency. That, and the doc that was put together didn't mention the summary line [14:39] cherylj: k [14:39] katco: I'm rebuilding from the beta2 tag in git, for line number references [14:40] cherylj: if I recall correctly, that summary line was a suggestion from the license text but is much less relevant for our use :) [14:40] ericsnow: yeah, I think you're right. [14:41] cherylj: LGTM [14:41] ericsnow: thanks! [14:42] mgz: so you're passing in SignV4Factory(...)? [14:42] mgz: because if you've switched the debug logger to stdout, and it's using v4, i have no explanation for why you're not getting output. [14:45] katco: https://pastebin.canonical.com/128887/ [14:46] katco: I am also mystified [14:46] mgz: i can never remember... does --debug collect the logs from the disparate machines? [14:47]