[01:54] <wallyworld> babbageclunk: for whenever, here's that PR to handle app removal https://github.com/juju/juju/pull/8423
[02:47] <babbageclunk> wallyworld: ok, having a look now
[02:47] <wallyworld> yay, ty
[04:06] <jam> wallyworld: thumper: hangout?
[04:06] <thumper> we are there
[04:06] <jam> k, I'll try reconnecting
[04:07] <jam> thumper: it seems stuck at "requesting to join the video call." very strange, trying to figure out what's up
[04:07] <thumper> yeah, we both had that
[04:07] <thumper> ctrl-f5
[04:07] <thumper> until it stops
[04:15] <babbageclunk> wallyworld: reviewed
[09:28] <jam> elmo: ping if you're around
[17:52] <bdx> https://bugs.launchpad.net/juju/+bug/1751849 - wtf is this
[17:52] <mup> Bug #1751849: ERROR secret key for user "<username>" not found <juju:New> <https://launchpad.net/bugs/1751849>
[17:58] <bdx> its juju demo week for my team here, not off to a good start with whatever ^ is - would appreciate some coverage there, thx thx
[19:00] <kwmonroe> bdx: wag here, but can you try adding another user and setting a controller name that doesn't already exist?  maybe the token is being expired after the first prompt for a controller name.
[19:00] <bdx> ahh
[19:01] <kwmonroe> i'm not saying that's the right behavior, but may be enough to get you going.
[19:02] <bdx> kwmonroe: sending register command per dm
[19:02] <bdx> go for it
[19:02] <kwmonroe> thumper: do you know off hand when registration strings from add-user get expired? re: bdx bug above
[19:03] <thumper> kwmonroe: single use I believe
[19:03] <thumper> but I don't think it is time based
[19:03] <kwmonroe> bdx: worked for me:
[19:03] <kwmonroe> Enter a name for this controller [pdl-aws]: mycloud
[19:03] <kwmonroe> Initial password successfully set for myuser.
[19:03] <bdx> no way
[19:04] <bdx> cool! now I feel silly
[19:04] <kwmonroe> thumper: could it be the case that the secret is thrown away before a valid controller name is accepted? bug 1751849
[19:04] <mup> Bug #1751849: ERROR secret key for user "<username>" not found <juju:New> <https://launchpad.net/bugs/1751849>
[19:05] <bdx> well check out what my user posted
[19:06] <thumper> I wouldn't think so
[19:06] <thumper> but I'm on a call just now
[19:06] <thumper> so not responsive
[19:06] <kwmonroe> roger that
[19:07] <kwmonroe> bdx: fyi i unregisterred myself from your controller.
[19:07] <bdx> https://imgur.com/a/Vt2nf
[19:08] <bdx> cool, thanks
[19:09] <kwmonroe> oof that image is weird bdx.  DM me another register command and i'll accept the default pdl-aws controller name.
[19:10] <bdx> possibly I should give you the perms like I did for the other user too
[19:11] <kwmonroe> ok, fwiw, the last one was for 'myuser' with 'login' access:
[19:11] <kwmonroe> mycloud*      -          myuser             login                          -         -     -  2.3.3
[19:12] <bdx> ok
[19:13] <bdx> here's another, not sure if it will be any better https://imgur.com/a/u07W3
[19:14] <kwmonroe> bdx: lgtm https://paste.ubuntu.com/p/pTycc7W35K/
[19:15] <bdx> kwmonroe: thanks for verifying
[19:16] <kwmonroe> np bdx, fyi i'm on 2.3.3-highsierra-amd64 as well.
[19:16] <bdx> man
[19:16] <bdx> idk then
[19:17] <kwmonroe> are you sure your user didn't run the register command twice?  or someone else ran it with his/her token?
[19:17] <kwmonroe> maybe ask them to do "juju register --debug XXXXX" to make sure the client is getting over to the controller.
[19:18] <kwmonroe> and fyi, i unregisterred pdl-aws from my client.  can't have you blaming me for insane cloud bills ;)
[19:20] <bdx> aha
[19:20] <bdx> thank you
[19:20] <bdx> well, I cant replicate the issue anymore either
[19:20] <bdx> I guess its fixed now
[19:20] <bdx> sorry about the noise
[19:25] <bdx> "are you sure your user didn't run the register command twice?  or someone else ran it with his/her token?" - this very well could have happened
[19:27] <bdx> possibly 5-10 minutes passed between the time when I registered the user and the time that the user actually ran the register command
[19:28] <kwmonroe> get your people in check bdx
[23:34] <kwmonroe> bdx: is bug 1751849 cool to be closed as user's user error?
[23:34] <mup> Bug #1751849: ERROR secret key for user "<username>" not found <juju:New> <https://launchpad.net/bugs/1751849>
[23:35] <kwmonroe> happy to try other things, but i don't know what else we can do given the inability to repro on my side.
[23:37] <anastasiamac> kwmonroe: hi o/
[23:38] <anastasiamac> kwmonroe: i'll mark it as incomplete.. without repro would be hard to fix :)
[23:42] <kwmonroe> anastasiamac: the fix would be to mine bitcoin on all the controllers that bdx shared with me, and then being like "it's fixed", but secretly we'd be having steak tonight.
[23:43] <anastasiamac> kwmonroe: :D
[23:43] <kwmonroe> or, what actually happened, i unregisterred all bdx's secrets and hope it's just working as designed ;)
[23:44] <anastasiamac> kwmonroe: the only thing i could think of is that this juju register string has already been used on another client... it's a one-time-only thing...
[23:45] <anastasiamac> to use it on a different client, you'd need to re-issue the token (the argument to register command)...
[23:45] <kwmonroe> yeah, +1 anastasiamac, i think that's what we concluded with bdx earlier.  there was a 5-10m window where he wasn't watching his people type that could have resulted in 2 ppl running that.  the 1st invalidating the registration key for the 2nd.
[23:47] <anastasiamac> kwmonroe: ack