search

canonical / mongodb-k8s-operator

Operator charm for MongoDB
Apache License 2.0
13 stars 15 forks source link

Failed to get pbm status errors #212

Closed gruyaume closed 8 months ago

gruyaume commented 11 months ago

Steps to reproduce

  1. juju deploy mongodb-k8s
  2. juju deploy sdcore-nrf
  3. juju integrate mongodb-k8s sdcore-nrf

Expected behavior

No errors

Actual behavior

Failed to get pbm status errors in charm.

Versions

Operating system: Ubuntu 22.04 Juju CLI: 3.1.6 Juju agent: 3.1.6 Charm revision: 6/edge (Revision 37) microk8s: v1.27.6

Log output

unit-mongodb-k8s-0: 07:37:32 ERROR unit.mongodb-k8s/0.juju-log Failed to get pbm status. non-zero exit code 1 executing ['/usr/bin/pbm', 'status', '-o', 'json'], stdout='{"Error":"get status of pitr: check for errors: get current epoch: get config: get: mongo: no documents in result"}\n', stderr=''
github-actions[bot] commented 11 months ago

https://warthogs.atlassian.net/browse/DPE-2874

MiaAltieri commented 11 months ago

Hi @gruyaume from what I can tell this is infact an issue in the log messages. I'm happy you noticed it since poor logging can impact how users understand the charm, thanks for pointing this out :)

The log messages come from the shared mongodb libraries (which are hosted & maintained on the VM side) right now there are two open PRs to fix this: 6/edge and 5/edge once these are merged we can update the libraries on the k8s side.

Other than that though, the charm should be functional. Did you encounter any functional errors (with your workflow above) or only the incorrect log?

gruyaume commented 11 months ago

Perfect, thank you @MiaAltieri