Skip to content
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

Extensions not enabled on clean deployment #239

Closed
arturo-seijas opened this issue Sep 7, 2023 · 6 comments
Closed

Extensions not enabled on clean deployment #239

arturo-seijas opened this issue Sep 7, 2023 · 6 comments
Labels
bug Something isn't working

Comments

@arturo-seijas
Copy link

Steps to reproduce

  1. Deploy postgresql-k8s with enabled extensions
postgresql_config = {
    "plugin_pg_trgm_enable": True,
    "plugin_unaccent_enable": True,
}
ops_test.model.deploy(
    "postgresql-k8s", channel="14/edge", config=postgresql_config, trust=True
)
## Expected behavior
The database ha the specified extensions enabled.

## Actual behavior
Although the charm configuration is fine when running a `juju status`, the extensions have not been enabled.


## Versions

<!-- Run `lsb_release -sd` -->
Operating system: Ubuntu 20.04.6 LTS

<!-- Run `juju version` -->
Juju CLI: 2.9.44-ubuntu-amd64

<!-- Model version from `juju status` -->
Juju agent: 2.9.44

<!-- App revision from `juju status` or (advanced) commit hash -->
Charm revision: 132

<!-- Run `microk8s version` -->
microk8s: None, this is a full k8s distro

## Log output
<!-- Please enable debug logging by running `juju model-config logging-config="<root>=INFO;unit=DEBUG"` (if possible) -->
<!-- Then, run `juju debug-log --replay > log.txt` and upload "log.txt" file here -->
Juju debug log: Not relevant

<!-- (Optional) Copy the logs that are relevant to the bug & paste inside triple backticks below -->


## Additional context
<!-- (Optional) Add any additional information here -->
@arturo-seijas arturo-seijas added the bug Something isn't working label Sep 7, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Sep 7, 2023

@dragomirp
Copy link
Contributor

Look like extensions behaviour is confusing and doesn't give an indication of when the changes are applied. We'll add a unit status update, to improve visibility.

@dragomirp
Copy link
Contributor

Should be solved in latest edge (rev. 159)

@dragomirp
Copy link
Contributor

Looks like we still need to do more checks here.

@dragomirp dragomirp reopened this Oct 20, 2023
@dragomirp
Copy link
Contributor

Investigating further, it looks to me that postgresql work as intended and the new failures happen due to some kind of race in the redis relation. Testing on a forked repo, tests (bar the SAML test) succeed consistently. Leaving this issue open until @arturo-seijas has a chance to confirm.

@arturo-seijas
Copy link
Author

I've been able to confirm it @dragomirp , and it seems like it might be related to the Indico charm itself.

I'm closing the ticket.

Thank you very much :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants