[06:07] <icey> roaksoax you mentioned that you thought that https://pastebin.ubuntu.com/p/Gf3qkQ6SzS/ was a cloud-init bug, resolved with the cloud-init in -proposed; do you have any bug reference that I can track, or further details about when you think the fix will be released? I run into it with the Juju snap in both candidate and edge, but not the stable vers
[06:07] <icey> ion (I run into a different juju bug semi-regularly there)
[13:35] <roaksoax> icey: i would need to look through my email thread and see if I find it
[13:39] <icey> no hurry roaksoax
[13:39] <icey> although I'd appreciate it :-D
[19:44] <ananke> how does one clear failed tests, other than re-running them?
[19:53] <roaksoax> ananke: there's an option to override failed tests
[20:05] <ananke> roaksoax: unfortunately, I am unable to find it. eg: https://imgur.com/a/yVC8HQ7
[20:06] <ananke> there is nothing in the context menu for the machine, specific test options just show 'hide metrics' or 'view previous t...'
[20:07] <ananke> I can mark the entire node as broken, then as fixed, but that seems to have no impact on individual tests
[20:10] <roaksoax> ananke: the machine is ready so you have no option
[20:11] <roaksoax> overrideing failed tests wont clear those tests that failed
[20:11] <roaksoax> would make the machine ready but still show there was a failed tests
[20:11] <ananke> right, so how does one clear those warnings?
[20:13] <ananke> I have tests that show as timed out, like that badblocks-destructive, and ones that show skipped (such as the smartctl-validate, because those are raid arrays). since the results of those tests are irrelevant, it would make sense to remove them
[20:33] <roaksoax> ananke: there's no way to force remove those, unless you actually remove them from the DB
[21:49] <ananke> roaksoax: that's a wee bit disappointing, perhaps I'll file it as a feature request on github
[22:34] <roaksoax> ananke: we dont track bugs on gh
[22:34] <roaksoax> ananke: we track them on lp
[22:34] <roaksoax> :)
[22:35] <roaksoax> ananke: but you can start a ux discussion on discourse.maas.io
[22:39] <ananke> ahh, thank you
[22:40] <ananke> today I discovered another thing that I may have to suggest: ability to disable ipv6 for squid
[22:41] <ananke> if your dns server returns AAAA records, yet you don't have ipv6 address, doing anything with built-in proxy is a crapshot