[02:46] hpidcock, wallyworld: easy review to fix new intermittent test failure (oops)? https://github.com/juju/juju/pull/11055 [02:49] oh, when you get out of your meeting is fine [02:55] babbageclunk: you could also just do a SameContext check with the call names slice [02:55] *SameContent [02:56] i guess ther emight be other ones there you want to ignore? [03:53] wallyworld, hpidcock: wiring up the multiwatcher worker: https://github.com/juju/juju/pull/11056 [04:41] wallyworld: no rush but would be good to get eyes on it https://github.com/juju/juju/pull/11054 [04:41] ok, soon, after meeting [04:53] hpidcock: lgtm, ty [04:55] thumper: just quickly testing locally, but the code looks good, one comment but it's not a showstopper [04:56] hpidcock: I'm doing the rename for you [04:56] 😃 [04:58] hpidcock: is that a smily face? [04:59] I hope so [04:59] I see a rectangle [04:59] yay unicode [04:59] you need yourself a real font bloated with emoji [05:01] hpidcock: https://github.com/juju/juju/pull/11056/commits/3ad00c0a401dcb4e8ca497c9e260bf9b79459113 [05:02] unicode smiley face here that thumper doesn't have [05:03] * thumper EODs [05:03] except for that really late call in four hours [09:23] stickupkid: Not too big: https://github.com/juju/juju/pull/11059 [09:39] manadart, this PR looks like it broke windows, just trying to work out why https://github.com/juju/juju/commit/1bf87fbf14c637e24f800e7f605a719cce1f7e9a [10:29] stickupkid: CMR redirect to migrated model is now ready for review: https://github.com/juju/juju/pull/11025 [11:42] manadart, https://github.com/juju/version/pull/7 [11:48] no jenkins job for version [11:48] :| [15:32] Small patch for intermittent test failure: https://github.com/juju/juju/pull/11060 [16:05] Closed that one and targeted 2.7 https://github.com/juju/juju/pull/11061 [16:53] juju status hangs even after I've restarted the agent on machine-0. what else should I try before nuking everything [16:54] and in a bigger context, I'm trying to figure out why one of the actions on my charm cannot import from charmhelpers. the dependency is in wheelhouse [16:55] it was working a while back, but I recently rebuilt it with upgraded dependencies [17:01] skay: status shouldn't hang though? you're running it from the client and it's hanging waiting for input from a machine agent? [17:03] rick_h: I don't know why it's hanging. I ran bash with lxc exec to get to the machine to restart its agent. I thought perhaps it was waiting on that [17:03] skay: can you run with --debug and see if there's any output? [17:06] rick_h: doing so now. https://paste.ubuntu.com/p/tdDZrNykkh/ guessing it will timeout waiting connect to the API adress. so, not the agent. [17:11] rick_h: I'm not sure what to check on my machine. I've checked for any juju services and only see the snaps https://paste.ubuntu.com/p/tW6TjZDb4R/ [17:13] hml, this is the fix for windows bootstrapping https://github.com/juju/juju/pull/11062 [17:13] hml, any chance of a CR? [17:13] stickupkid: sure [17:14] if we ever do a 2.7 dev release, it'll break there, so I'll have a look at back porting it [17:15] stickupkid: rgr, [17:25] * skay afks a bit [17:27] skay: sorry, watching the town hall. Yes that looks like the client cannot reach/connect to the controller [17:27] skay: so curious if you can ping/ssh to that machine/ip [17:29] rick_h: yes. whoops. forgot about the th [17:35] rick_h: ok, so it's weird. lxc list doesn't show a machine with that IP. anyway, I ssh'd in and restarted jujud and juju-db. status worked. it shows one machine down! let me check the log to see if the weirdness happened with the password [17:43] skay: :/ [17:45] rick_h: oh wait, it's not down. maybe I was looking at the wrong screen [17:45] skay: ok apologies but the whole thing is confusing to me at this point [17:45] rick_h: no, it was down, but no longer. yeah, me too. sorry. [17:45] * rick_h tries to be helpful by just standing still lol [17:45] if I managed to ever reproduce the down machine situation in a less confusing way I will ping back here [17:46] definitely, always eager to find issues/get them addressed [17:47] I am seeing this in the logs, I'm not sure what's up with that. but let me keep working since things are just confusing at this point. https://paste.ubuntu.com/p/RMnw4FwxSW/ [17:49] skay: hmmm, that's failure for a controller to connect to mongodb and looks like it's trying locally [17:49] skay: might be worth checking syslog/mongodb logs to see if it's not happy [17:49] if your db is unhappy state can be fishy [17:52] I think it is unhappy https://paste.ubuntu.com/p/g8BQhKCwz8/ [17:52] I'm going to afk for real a while now [17:53] skay: hmm yea that's going to be an issue and cause the controller to restart/not work [20:05] Here's a PR that was very satisfying: https://github.com/juju/juju/pull/11063 [21:10] back again from context switch [21:10] I have an action that is failing because it cannot import charmhelpers. my action imports action_ from hookenv. [21:11] it worked about a year ago. has anything changed drasticly such that I need to rewrite my action? I am baffled [21:11] skay: I know in the last year we changed so it only pulls from the venv and not system packages by default any longer [21:11] rick_h: ok, so I'm running debug-hooks and actually wondering where the venv is! [21:12] I couldn't find it. I figured it must be getting invoked somehow? [21:12] I want to verify that the packages I think I'm installing are actually installed (I am guessing 100% they are not) [21:15] though wait, my reactive stuff is able to import charmhelpers. I am feeling pretty stupid [21:17] do I have to change my action to activate the venv? ew? [21:17] probably? [21:17] since actions are in a different folder and not dispatched with the framework addons [21:17] so you'd need to activate the venv/set your python path to the venv to share libaries/etc [21:20] hmm. where is the venv so that I can do that? [21:21] I don't know what path to add [21:23] the docs for writing actions show an example in bash, so they get to use the command line tools [21:27] skay: you'll have to look into instance. on the phone atm, sudo updatedb && locate python | grep bin ? [21:28] got it. thanks! [22:46] thanks wallyworld for the review [22:51] np === aluria` is now known as aluria