-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Charm cannot be installed on an Juju managed LXD machine. #354
Comments
Hi, @moisesbenzan, are there any storage pools available to Juju? It looks to me that Juju can't provision a volume for Postgresql. |
@moisesbenzan Is it still reproducible after adding storage pool? |
I think this behaviour is entirely controlled by Juju. |
Below is my test on top of openstack. Confirm there's cinder storage-pools available. Deploy postgresql with Found an old discussion - https://chat.charmhub.io/charmhub/pl/obumb6guybf8fmm4jhj9w1tuxh, which seems to be a charm problem? |
Hi @jeffreychang911 @moisesbenzan that behavior is controlled by juju. I have issued this bug with them: https://bugs.launchpad.net/juju/+bug/2060098 Would be nice meanwhile to avoid LXCs for DB and deploy the workloads directly on VMs instead. |
My $0.05, I second to @dragomirp and @phvalguima: it is the current limitation of Juju, IMHO. re: @jeffreychang911 I disagree. The reply there is: All the modern Data team charms (PostgreSQL, MySQL, MongoDB, ... ) uses juju storage. Let's continue in https://bugs.launchpad.net/juju/+bug/2060098 and see the Juju team feedback there. P.S. we are happy to improve something on our side here, but on this stage our charm.py code is not yet even launched. |
We've got reply from Juju Team: Resolved as nothing to fix in PostgreSQL charm? |
That would be ok, thanks. |
Resolving as agreed. |
Steps to reproduce
juju deploy --channel 14/edge --model postgresql --to lxd postgresql
Expected behavior
Unit would be assigned correctly to an LXD machine provisioned via Juju
Actual behavior
Versions
Operating system: Ubuntu 22.04
Juju CLI: 3.1.7
Juju agent: 3.1.7
Charm revision: 14/edge 367
LXD:
5.0.3-51452c3, rev. 26881
Log output
Juju debug log:
Not captured in this run.
Additional context
The text was updated successfully, but these errors were encountered: