[11:04] ¡Muy buenos días a todos! [12:32] cory_fu: can you let me know if I'm doing something wrong using https://github.com/juju-solutions/resource-oci-image/ in https://code.launchpad.net/~mthaddon/charm-k8s-openldap/+git/charm-k8s-openldap/+merge/395418 ? I don't think it's passing in the correct username and password, but I'm not sure how to determine what it is passing in [12:44] cory_fu: er, I suppose I should explain the problem I'm having... getting "Error: ErrImagePull" in juju status from "juju deploy cs:~mthaddon/openldap; juju deploy cs:~postgresql-charmers/postgresql-k8s postgresql; juju add-relation openldap:db postgresql:db" in a k8s model [16:51] bthomas: do you know if there's a way of doing https://github.com/canonical/prometheus-operator/blob/master/actions/reload-config in the operator framework itself rather than as a standalone script like that? (i.e. execute a command on a k8s pod and check the output) [16:53] mthaddon: From what I remember actions were not supported in the Python framework. Chipaca may have created and issue for this. I have not checked if the situation has changed in a recent version. [16:53] ack, let me see if I can find a relevant issue [16:55] I can't find anything relevant, I'll file an issue - thx [16:55] looking myself but do not find any such issue [17:00] Issue operator#464 opened: How to run a command on a k8s instance via an action [17:21] mthaddon: I'm out, but the helper only fetches and slightly transforms the data it gets from the Juju resource to match the format expected by the pod-spec. If you're getting an ErrImagePull it means either the resource info is missing, wrong, or your cluster can't talk to whatever image repo the resource is pointing at. `charm show cs:~mthaddon/openldap resources` shows a resource and `charm pull-resource cs:~mthaddon/openldap openldap [17:21] -image` works fine for me locally ("Status: Downloaded newer image for registry.jujucharms.com/mthaddon/openldap/openldap-image@sha256:78364e2d5df6362a0cbff65285e9c22904af05ae6a28e91a7263a6ba04bb2495") so it sounds like your cluster can't talk to registry.jujucharms.com for some reason. [17:24] mthaddon: Usage in the MR looks fine. HTH [17:40] cory_fu: thx for the info, will dig a bit deeper [23:43] mthaddon: super late response, but the issue with actions isn't correctable in the framework. They are not currently supported by Juju on K8s. I believe they were in-cycle to get added, I'll follow up with the team tomorrow.