| facubatista | ¡Muy buenos días a todos! | 10:11 | 
|---|---|---|
| bthomas | morning facubatista | 10:13 | 
| facubatista | hola bthomas | 10:14 | 
| bthomas | 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="<root>=DEBUG;<unit>=DEBUG" update-status-hook-interval=1m. Any idea ? | 10:23 | 
| facubatista | bthomas, if you do a print(), do you see it? | 10:27 | 
| bthomas | will try now | 10:28 | 
| bthomas | 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:31 | 
| facubatista | bthomas, are you running `juju debug-log` without further restrictions? | 10:32 | 
| bthomas | facubatista: yes just "juju debug-log" | 10:32 | 
| facubatista | bthomas, if you run the hook manually inside the machine, do you see that output? | 10:34 | 
| bthomas | 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:40 | 
| bthomas | doing so gives me KeyError: 'JUJU_UNIT_NAME' in ops/model.py | 10:43 | 
| facubatista | bthomas, no, you need to run it under the juju environment | 10:43 | 
| facubatista | bthomas, tell juju to open a terminal for you in that context | 10:44 | 
| facubatista | bthomas, this is with `juju debug-hooks` | 10:45 | 
| bthomas | facubatista: got it. I need to upgrade to juju 2.9 for that . Will do that now. | 10:46 | 
| facubatista | FWIW https://discourse.charmhub.io/t/command-debug-hooks/1705 | 10:46 | 
| bthomas | facubatista: after upgrade to juju 2.9/candidate I am now seeing the debug lines being printed out. | 10:59 | 
| facubatista | bthomas, wonderful! | 11:09 | 
| Chipaca | moin moin | 11:09 | 
| Chipaca | facubatista: what's wonderful? | 11:09 | 
| facubatista | Chipaca, that bthomas sees debug lines | 11:10 | 
| Chipaca | 🙂 | 11:10 | 
| Chipaca | bthomas: is that call still needed then? | 11:10 | 
| bthomas | facubatista: Chipaca : sorry please wait the problem seems to be occuring again on redeploying my charm. | 11:10 | 
| bthomas | I need that meeting Chipaca . Going to grab a quick coffee. Need that coffee too. | 11:11 | 
| bthomas | I am going to restart microk8s | 11:20 | 
| bthomas | problem still exists | 11:26 | 
| JoseMasson | Good morning! | 12:14 | 
| bthomas | morning JoseMasson | 12:30 | 
| bthomas | 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:18 | 
| * bthomas gets ready to nuke everything | 13:41 | |
| bthomas | wow juju status is just hung or taking too long | 13:45 | 
| bthomas | microk8s status is fine | 13:45 | 
| bthomas | took too long | 13:45 | 
| bthomas | reboot brb | 14:00 | 
| * bthomas -> coffee | 15:11 | |
| Laney | 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:04 | 
| Laney | with reactive I would use the apt layer for that, something that provides equivalent funcitonality | 16:05 | 
| Chipaca | Laney: there aren't, no | 16:05 | 
| Laney | or maybe I could crib from existing work, but I don't see a link to the code on charmhub.io | 16:05 | 
| Chipaca | 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:19 | 
| Laney | Chipaca: I see, maybe I'm weird because I often start with 'install git, clone repo' :-) | 16:20 | 
| Chipaca | Laney: is this for k8s? | 16:20 | 
| Laney | nein | 16:20 | 
| Chipaca | Laney: k | 16:20 | 
| Laney | ah well, I guess subprocess.check_call is there | 16:21 | 
| Chipaca | Laney: is the thing you need to install needed for the charm itself, or for the application it drives? | 16:22 | 
| Laney | Chipaca: It's the latter, at least right now, so this is fine | 16:24 | 
| Laney | I guess requirements.txt would work for the former case, at least for stuff on pypi? | 16:24 | 
| Laney | probably won't need this though, the charm is going to be quite thin I think | 16:24 | 
| Chipaca | Laney: requirements.txt also can point to github etc if it's not on pypi (as long as it's pip-installable) | 16:25 | 
| Laney | nod | 16:25 | 
| Chipaca | ie has a setup.py | 16:25 | 
| * Chipaca steps away for a while | 17:10 | |
| * Chipaca lied | 17:13 | |
| * Chipaca EODs | 18:01 | |
| * bthomas EODs | 18:05 | |
| * facubatista bbl | 18:35 | |
| * JoseMasson steps away for a while | 19:40 | |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!