[02:52] <blr> Are there any known race conditons when using apt-mirror and apt-http-proxy? juju is unable to acquire a dpkg lock.
[02:53] <sarnold> blr: a dpkg lock is entirely local to the one computer; probably another apt process is running on the machine, perhaps via unattended-upgrades or another mechanism; ps auxw | grep -i apt  would probably point it out
[02:55] <blr> sarnold: fairly certain there is no other apt process other than that used by juju, and this only seems to occur when using apt-mirror.
[02:57] <sarnold> blr: hmm, I haven't tried apt-mirror, but it doesn't feel like something I'd expect to happen..
[02:58] <blr> sarnold: I am running squid-deb-proxy locally with apt-http-proxy, which is potentially relevant.
[02:58] <sarnold> blr: I use squid-deb-proxy too, lovely thing :) hehe
[02:59] <blr> sarnold: oh goodness yes.
[02:59] <blr> particularly when you're in new zealand, and archive.ubuntu.com isn't exactly fast :)
[02:59] <sarnold> blr: owwwwwww
[02:59] <sarnold> blr: it's not even fast from .us  :)
[02:59] <blr> heheh
[03:00] <sarnold> .. I can't imagine, those poor kiwis trying to move all those packets
[03:00] <blr> there's a reason they're endangered.
[03:00] <sarnold> hehe :) good luck sorting it out, I'll be curious to hear what might cause your lock problem
[03:02] <blr> yeah, bit of an odd one. Once my local cache is warm it isn't a big deal, but would be nice to have both the mirror and the apt proxy working together.
[09:28] <Flopy69> Helllo!
[09:28] <Flopy69> What are the things to check when "JuJu sync-tools" does not work?
[14:13] <hazmat> Flopy69: depends on the error.. pastebin?
[15:15]  * lazyPower puts on his charm reviewer hat
[15:15]  * lazyPower flips on the head lamp and dives into teh review queue
[15:38] <lazyPower> https://github.com/whitmo/bundle-kubernetes - if someone has 5 minutes, a brief once over and a "yes i feel confident i have enough information to dive in with this readme" would be great.  we're having a bit of an internal debate on how much wall of text we need to add here  or if its a no - pointers to what you feel are hazy is invaluable to me
[15:44]  * whit|review-q puts on review cape
[15:59] <whit|review-q> is there a reference for all the environment variables one can set to affect the behavior of the juju client?
[15:59] <whit|review-q> hiya hazmat!
[16:02] <lazyPower> whit|review-q: not to my knowledge
[16:02] <hazmat> whit|review-q: greetings
[16:02] <hazmat> whit|review-q: there is in the public docs, its mostly up to date even ;-)
[16:03] <whit|review-q> hazmat, I remember you commenting on that in the past...
[16:03]  * whit|review-q goes to find it
[16:03] <hazmat> whit|review-q: yeah. its been mostly resolved since then
[16:03] <whit|review-q> https://juju.ubuntu.com/docs/reference-environment-variables.html
[16:03] <lazyPower> nice
[20:35] <lazyPower> mbruzek: https://bugs.launchpad.net/charms/+source/openmanage/+bug/1420475  - as promised
[20:35] <mup> Bug #1420475: CI infrastructure reports failure due to hardware limitations <openmanage (Juju Charms Collection):New> <https://launchpad.net/bugs/1420475>
[20:58] <wwitzel3> blahdeblah_: were ever able to figure out if you could get me access to that juju env? re: https://bugs.launchpad.net/juju-core/+bug/1417875
[20:58] <mup> Bug #1417875: ERROR juju.worker runner.go:219 exited "rsyslog": x509: certificate signed by unknown authority <canonical-bootstack> <logging> <regression> <juju-core:Triaged by wwitzel3> <juju-core 1.21:Triaged by wwitzel3> <juju-core 1.22:Triaged> <https://launchpad.net/bugs/1417875>
[22:06] <blahdeblah_> wwitzel3: I've got a meeting about it this morning; I'll ask the question again.
[22:06] <blahdeblah_> wwitzel3: What's the best launchpad group to subscribe to the repo, once it's approved?