[10:11] ¡Muy buenos días a todos! [10:13] morning facubatista [10:14] hola bthomas [10:23] facubatista: I am not seeing any of my logger.debug() output showing up in juju debug-log , even though I have set juju model-config logging-config="=DEBUG;=DEBUG" update-status-hook-interval=1m. Any idea ? [10:27] bthomas, if you do a print(), do you see it? [10:28] will try now [10:31] facubatista: no I do not see print() output either. What all could be wrong. I can dig to see which of them is true. [10:32] bthomas, are you running `juju debug-log` without further restrictions? [10:32] facubatista: yes just "juju debug-log" [10:34] bthomas, if you run the hook manually inside the machine, do you see that output? [10:40] facubatista: do you mean just ./hooks/start in /var/lib/juju/agents/unit-tester-0/charm ? (tester is my charm). I am logged into the operator pod tester-operator-0 ? [10:43] doing so gives me KeyError: 'JUJU_UNIT_NAME' in ops/model.py [10:43] bthomas, no, you need to run it under the juju environment [10:44] bthomas, tell juju to open a terminal for you in that context [10:45] bthomas, this is with `juju debug-hooks` [10:46] facubatista: got it. I need to upgrade to juju 2.9 for that . Will do that now. [10:46] FWIW https://discourse.charmhub.io/t/command-debug-hooks/1705 [10:59] facubatista: after upgrade to juju 2.9/candidate I am now seeing the debug lines being printed out. [11:09] bthomas, wonderful! [11:09] moin moin [11:09] facubatista: what's wonderful? [11:10] Chipaca, that bthomas sees debug lines [11:10] 🙂 [11:10] bthomas: is that call still needed then? [11:10] facubatista: Chipaca : sorry please wait the problem seems to be occuring again on redeploying my charm. [11:11] I need that meeting Chipaca . Going to grab a quick coffee. Need that coffee too. [11:20] I am going to restart microk8s [11:26] problem still exists [12:14] Good morning! [12:30] morning JoseMasson [13:18] I am seeing the same no logging issue again. I am going to take a break have some lunch, then get back to it. I plan to kill controller, snap remove juju, maybe even microk8s and recreate the full environment and see if it solves my problems. Odd thing is I made no changes to my system since yesterday. Nothing I did could have caused these problems. [13:41] * bthomas gets ready to nuke everything [13:45] wow juju status is just hung or taking too long [13:45] microk8s status is fine [13:45] took too long [14:00] reboot brb [15:11] * bthomas -> coffee [16:04] hi operators, I'm just trying to write a simple charm with this framework. What I'm wondering is... are there helper libraries for common things like installing dependencies from the Ubuntu archive? [16:05] with reactive I would use the apt layer for that, something that provides equivalent funcitonality [16:05] Laney: there aren't, no [16:05] or maybe I could crib from existing work, but I don't see a link to the code on charmhub.io [16:19] Laney: it was on our rader as what we expected would be one of the most demanded things, but in the end it wasn't [16:20] Chipaca: I see, maybe I'm weird because I often start with 'install git, clone repo' :-) [16:20] Laney: is this for k8s? [16:20] nein [16:20] Laney: k [16:21] ah well, I guess subprocess.check_call is there [16:22] Laney: is the thing you need to install needed for the charm itself, or for the application it drives? [16:24] Chipaca: It's the latter, at least right now, so this is fine [16:24] I guess requirements.txt would work for the former case, at least for stuff on pypi? [16:24] probably won't need this though, the charm is going to be quite thin I think [16:25] Laney: requirements.txt also can point to github etc if it's not on pypi (as long as it's pip-installable) [16:25] nod [16:25] ie has a setup.py [17:10] * Chipaca steps away for a while [17:13] * Chipaca lied [18:01] * Chipaca EODs [18:05] * bthomas EODs [18:35] * facubatista bbl [19:40] * JoseMasson steps away for a while