Avoid pebble injection if OCI ships pebble
Bug #2031117 reported by
Alex Lutay
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Hi,
Data Platfrom team has faced the following situation:
* Pebble has implemented new feature to shutdown DB safely: https:/
* Juju 2.9.44 and Charm have migrated on new Pebble: https:/
* User noticed degradation on 2.9.42: https:/
Proposal: juju will stop injecting pebble into OCI is pebble is available there already.
We can ship latest (compatible with charm.py) version into our OCI => users will be able to run charm using old Juju 2.9.42.
Tnx!
P.S. The long internal discussion is here: https:/
tags: | added: canonical-data-platform-eng |
To post a comment you must log in.
I don't think we can agree to this - we could run into some pretty hairy problems if Juju is expecting certain features to be available in the Pebble, but the version shipped in the container doesn't support them.
This feels like a pretty easy way for us to introduce uncertainty and instability.