kelvinliuty hpidcock00:00
kelvinliuwallyworld: yes, I will have a pr for 2.700:00
wallyworldno need for a 2.7 fix, they claimed it was working in 2.700:01
wallyworldso i was curious if we had introduced a regression in 2.800:01
wallyworldkelvinliu: i think we're ok to $$mergre$$ into 2.8?00:06
kelvinliuwallyworld: we have this for legacy podspec in 2.700:08
kelvinliuand podspecV2 in 2.800:08
wallyworldso v3 is ok?00:09
kelvinliulatest/current podspec has no issue00:09
kelvinliucoz only previous version can have ProviderPod == nil00:10
wallyworldlet's land in 2.8 so we can get the release candidate built. we're not doing any more 2.700:10
wallyworldkelvinliu: here the port of the 2.8 fix https://github.com/juju/juju/pull/1214300:44
kelvinliuwallyworld: lgtm thx for doing this port pr00:47
thumperhow's things going?01:06
wallyworldgetting 2.8.6 candidate packaged today, 2.9 beta as well, so busy01:07
thumperhow's the new k8s stuff going?01:08
wallyworldhaving "fun with leadership/locks" on heavily loaded microk8s deployments01:08
wallyworld2.9 beta will allow a POC/MVP charm with v2 metadata to be tried01:08
thumperhow does it feel to use?01:10
wallyworldhard to say because it's not much more than a simple pod with a stateful set. so all the other things people use not there yet01:11
wallyworldv2 metadata much better though (not just for k8s), it ditches series in favour of os/version/arch01:12
wallyworldkelvinliu: to help debug the k8s dex-auth issue, i've added extra logging https://github.com/juju/juju/pull/1214402:47
wallyworldwe'll also want to run the kubeflow CI tests with TRACE turned on for02:47
kelvinliuwallyworld: lgtm, will just set the root to trace02:55
wallyworldthat will be a lot of trace, might load it up even more02:55
kelvinliuwe only have those logs uploaded if the tests failed02:57
kelvinliuso it might be ok, u know we can't change this whenever we want see something different,03:01
wallyworldkelvinliu: yeah, we can't change, but my thought was trace for everything would make things worse, as opposed to just trace for those selected packages. but we can try with trace for root and see03:08
kelvinliuyeah the logger sender would be more busy03:12
wallyworldkelvinliu: ah, i landed that logging PR to develop not 2.8. will have to do another PR03:55
kelvinliuwallyworld: u wanna change the log level for both controller and model, right?03:57
wallyworldyeah, lets03:57
wallyworldkelvinliu: here's the backport https://github.com/juju/juju/pull/1214503:58
kelvinliujust set the logging level to trace for ken's pr04:01
wallyworldgreat ty, i'll get the 2.8 edge snap built as soon as the PR lands04:01
wallyworldhopefully we can then trigger a run manually04:02
manadartachilleasa: Can you take another look at https://github.com/juju/juju/pull/12118 ? I reverted the change to return NoSupported, because there are so many test suites that use the method. I'll use an alternative and clean it all up in a later patch.08:04
achilleasamanadart: still got a failing client test08:26
=== mup_ is now known as mup
achilleasamanadart: or stickupkid can either of you take a quick look at a small typo fix? https://github.com/juju/juju/pull/1214710:04
stickupkidmanadart, I've just disabled the test for now https://github.com/juju/juju/pull/1214810:26
manadartstickupkid: Ack.10:27
stickupkidmanadart, https://github.com/juju/juju/pull/1214910:32
eloxHey, I'm struck by a bug I would like some help in understanding how to resolve. I get an error from pip when trying to install PyYAML which seems to come from the reactive framework. It blows up my installation of nextcloud. Here is a screenshot of the error. https://pasteboard.co/JvUDbhx.png13:09
Chipacaelox: looks like the error is from trying to _uninstall_ pyyaml13:38
Chipacaanyway, probably not helpful :-/13:38
manadartNeeds review: https://github.com/juju/juju/pull/1215114:04

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