kfp-profile-controller/0* waiting idle 10.1.67.32 [container:kfp-profile-controller] Waiting for Pebble services (kfp-profile-controller). If this persists, it could ...
However, our CI tests have been passing, even after having merged the breaking PR https://github.com/canonical/kfp-operators/pull/414. This means that our tests are not catching that the charm is not active. Thus, we should fix that
Bug Description
Tackling https://github.com/canonical/kfp-operators/issues/487, we figured out that kfp-profile-controller charm built from
track/2.0
would never go active but would instead stay inwaiting
foreverHowever, our CI tests have been passing, even after having merged the breaking PR https://github.com/canonical/kfp-operators/pull/414. This means that our tests are not catching that the charm is not active. Thus, we should fix that
To Reproduce
Rerun the CI and observe juju status
Environment
Juju 3.5.0 microk8s 1.28
Relevant Log Output
Additional Context
No response