[00:00] right - that confirms that it's code running inside the container that can't get to the lxd port. [00:00] dmitri-s: ^ [00:01] So my LXD config is incorrect? [00:01] I think so [00:02] Just tried curl from inside a container and it times out (curl: (7) Failed to connect to 10.208.133.1 port 8443: Connection timed out) [00:02] wallyworld: got this PR to add pod addresses to binding addresses for CaaS, could u take a look? thanks! https://github.com/juju/juju/pull/10741 [00:03] i can, just need to get some stuff done first [00:04] np, not urgent at all [00:05] dmitri-s: sorry, just trying to work out what config needs to change... [00:06] Here is my current lxd config (lxd init --dump) https://github.com/dmitri-s/juju-learn/blob/master/lxd_config [00:07] oh thanks [00:07] comparing that to mine... [00:11] dmitri-s: the only difference I can see is that I have `core.proxy_ignore_hosts: 127.0.0.1,::1,localhost` in the config section. [00:11] what does `route -n` show inside the container? [00:12] root@pleasant-bonefish:~# route -n [00:12] Kernel IP routing table [00:12] Destination Gateway Genmask Flags Metric Ref Use Iface [00:12] 0.0.0.0 10.208.133.1 0.0.0.0 UG 100 0 0 eth0 [00:12] 10.208.133.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 [00:12] 10.208.133.1 0.0.0.0 255.255.255.255 UH 100 0 0 eth0 [00:13] and obviously you can get to the internet from the container since we can see things installing in the juju log... [00:14] (the route output looks the same as mine) [00:16] interesting [00:16] Sorry, this is about the point I'd ask in #lxcontainers [00:17] thanks. I will do that. BTY, was I supposed to post this in discourse.jujucharms.com rather than ask here? [00:17] just so I know next time. [00:17] Just from the server message "https://jujucharms.com, general chat on https://discourse.jujucharms.com" [00:18] seems like it is where it point me [00:19] No, this is a good place too, especially for back-and-forth. Although the advantage of discourse is that it's persistent - if people aren't in the same timezone then they won't see irc chat but they can still answer posts. [00:20] cool. thanks for your help. [00:21] no worries - sorry I couldn't sort it out fully [00:21] (or at all) [00:25] haha... movement in any direction is progress as I see it. I figured out that "x.x.133.1" is a gateway, so it is a progress. [00:26] With your help, nothing less. :) [00:26] :) [00:56] kelvinliu: free now in standup [00:56] yep [02:46] kelvinliu: lgtm with some suggested cleanup to make things more logical now that the behaviour has changed [02:47] wallyworld: yeo thx [02:47] yep* [03:11] wallyworld: for post-lunch digestion, PTAL https://github.com/juju/juju/pull/10746 - 'show-cloud' ask-or-tell [03:12] ok [03:12] just getting coffee [03:12] oh good! o the timing is right for light reading :D [03:33] anastasiamac: i asked a question, see if i am being dumb [03:33] babbageclunk: i pushed a change to address the race, see what you think? [03:34] wallyworld: kind of ;) i'll reply on pr [03:42] anastasiamac: s/kind of/most definitely. lgtm [03:43] wallyworld: :) it was existing code anyway that I have just prettied up :) [03:43] yeah, i didn't see that from the review diff, just mainly saw the comment etc [03:44] wallyworld: thank you for the review tho \o/ really appreciate another set of eyes [03:44] more eyes always good [03:52] wallyworld: approved [03:52] \o/ tyvm [04:02] babbageclunk: call? [04:02] oops [04:47] babbageclunk: another https://github.com/juju/juju/pull/10747 [04:47] or wallyworld ^^ [04:47] oooh instancepoller, my favourite [04:50] * thumper EODs [05:42] wallyworld: PTAL https://github.com/juju/juju/pull/10748 - 'show-credential' part [05:42] ok [08:56] nammn_de, good catch last night, yes if you hold it differently it breaks, I fixed it so both ways works https://github.com/juju/juju/pull/10749 [09:11] stickupkid: cool, approved :D [09:26] rick_h I just scrolled through the systemd code and found out that we do a verify an a basic level. So I don't think we need to add additional checks. So IMO the pr is ready to be reviewed https://github.com/juju/juju/pull/10696 [09:29] wallyworld: Is there are a resolution for all apps in a CAAS model getting "already exists" errors for generating secrets? [09:29] manadart: regarding the bug you mentioned before with the charm version. I did add some additional test, which does not include the bug yet, but still include some other cases. https://github.com/juju/juju/pull/10744 , when we "fix the bug" we could add the other cases as well. [09:29] Additionally I updated the bug description with my debugging output https://bugs.launchpad.net/juju/+bug/1848149 . I planned to take this on later [09:29] Bug #1848149: Charm Deployed or Upgrade from Dir Ignores "version" [09:30] nammn_de: Ack. [09:30] wallyworld: for example: "creating secrets for container: tensorboard: secret "tensorboard-tensorboard-secret" already exists" [09:37] achilleasa stickupkid : im trying the qa steps from hml https://github.com/juju/juju/pull/10718 there are some things I don't know. Got some time and want to have fun walking me through a little with a little qa? Doesn't have to be now [09:49] jam: shouldn't this (https://github.com/juju/juju/blob/develop/worker/instancepoller/updater.go#L140-L145) check use the instance status (which can be running) instead of the machine status (AFAICT would be created)? Or are statuses working differently for manual machines? [10:22] manadart: if you have some free time https://github.com/juju/juju/pull/10691 pr regarding spaces. Sadly I do have some weird network issues and my internal upgrade bootstraps got stuck (qa steps) [10:47] nammn_de: Reviewed. Upgrade step needs another look. [11:48] manadart: Just read it, good to know for me! Thanks [12:39] nammn_de: for 10691 you probably also need to patch this: https://github.com/juju/juju/blob/develop/cmd/juju/application/upgradecharm.go#L757 [12:40] manadart: added your suggestions, qa steps worked for me! [12:41] achilleasa, manadart :" ohh, nvm me than I ll take a look [12:44] achilleasa: are we fine to use the default if none is set, which should be set in any case with my patch? [12:46] anyone know where the simple streams url is in the source code? I know we have a model config value, but it's empty, so we must fill it in with something if it's empty. [12:47] nammn_de: I 'd say leave it for now to be safe in case someone is testing the new client against a controller from a sha before your PR landed [12:48] achilleasa: not patching this function at all or you mean adding a check if it exists, use it? [12:49] nammn_de: if the model (it's passed an an arg to that function) defines it use that or use the network.DefaultSpaceName as a fallback [12:51] achilleasa: thanks. Similiar to that? https://github.com/juju/juju/blob/ef08716950173d3a388d675b5c49c1210137c050/cmd/juju/application/upgradecharm.go#L761-L760 [12:53] achilleasa: IIRC, MachineStatus is the status of the machine agent, vs the status of the machine itself [12:54] jam: that's my understanding as well. So can this be ever running? [12:54] (in running state) [12:54] achilleasa: I'm really not sure what it is trying to check there. It may just be trying to say "set it to running if it isn't running" [12:55] yes, but I would assume that the check would be more like "if my *instance* status is not running and I am a manual machine then set me as running" [15:09] stickupkid: can you please check if this works on develop for you? go test -check.v -check.f TestAgentSetsToolsVersion (in cmd/jujud/agent) [15:10] achilleasa, why is that? [15:11] stickupkid: https://pastebin.canonical.com/p/pf5wXMFmtD/ [15:11] wtf is that [15:12] I will retry on current HEAD [15:12] achilleasa, https://pastebin.canonical.com/p/J86Vg3z53B/ [15:13] this fails on HEAD for me: "FAIL: machine_test.go:607: MachineLegacyLeasesSuite.TestAgentSetsToolsVersionManageModel" [15:14] could it be deps? brb [15:15] nope... still failing [15:16] manadart: time for a quick review? I added your and achilleasa suggestions https://github.com/juju/juju/pull/10691/files [15:16] stickupkid: wonder if that test is actually pulling stuff from somewhere... [15:16] achilleasa, we should have a look at what the test does [15:18] stickupkid: L598 [15:20] achilleasa, ho? [15:21] omw [15:25] nammn_de: Needs another change. I have to run. [15:30] hml: are you on eoan? [15:30] achilleasa: not yet [15:30] hml, go test -check.v -check.f TestAgentSetsToolsVersion [15:31] hml, ho in daily [15:31] stickupkid: omw [15:34] rick_h: are you on eoan? [15:36] also nammn_de are you on eoan? [15:36] achilleasa: yesss [15:36] manadart: thanks, damnit [15:37] can you join daily please? [15:38] nammn_de: ^ [15:40] nammn_de: actually can you please run go test -check.v -check.f TestAgentSetsToolsVersion (in cmd/jujud/agent) and let me know if it fails for you? [15:40] achilleasa: yes, I'm on eoan [15:41] rick_h: can you try the above command ^^ [15:41] achilleasa: the test command? [15:41] yeap. I think it fails on eoan [15:42] (only) [15:46] achilleasa: I'll see. I need to setup a dev environment on here. I've not done that yet. [15:46] achilleasa: heads up in case you didn't see it https://github.com/juju/juju/pull/10747#event-2720070282 [15:46] achilleasa: might be worth pulling and making sure that there's no issues in overlap/etc [15:47] rick_h: thanks, already incorporated that in my PR [15:47] achilleasa: awesome [15:58] achilleasa: sorry wasnt there, still need me? [15:59] achilleasa: ah i see not needed anymore [16:05] manadart: reverted the change [16:06] achilleasa: Can you approve that^ one? [16:07] manadart: one sec [16:07] Got hands full with kids here. Not at PC. [16:14] nammn_de: approved [16:30] achilleasa, any news? [16:33] Need a review for https://github.com/juju/juju/pull/10751. [16:56] manadart: one for tomorrow: https://github.com/juju/juju/pull/10750 [16:56] thanks manadart achilleasa [17:15] Having some trouble getting the apt layer to install a ppa. It seems to be ignoring whatever I put in. Maybe a yaml level problem? Are there any working examples that show a full layer.yaml with adding a ppa? [17:34] stub: where is the best place to go for more info on the apt-layer? I am obviously missing something. [19:51] morning [19:58] morning thumper [21:21] thumper: if you get time can you peek back at nam's branch for the log permissions please? [21:21] rick_h: will do [21:22] <3 [21:57] mbeierl: https://github.com/stub42/layer-apt has the README rendered [22:21] can I get a review for this merge? https://github.com/juju/juju/pull/10752 [22:25] babbageclunk: on it [22:28] merci m'sieur