-
Notifications
You must be signed in to change notification settings - Fork 71
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
datastore not provisioning #2565
Comments
Hi @BartNetJS ! Thanks for opening this issue. Could you provide a bit more info about your setup?
If you could also provide steps to reproduce, that would be awesome! |
Hi @adnanrahic The version is 0.11.8 The provision.yaml file exist in the config folder: I tried a helm install and helm upgrade. The initial yaml file was created with I've changed the url for the jaeger instance and did an upgrade.
And then deleted the release and deployed again. |
And an issue with the url if tracetest is configured with the suffix /tracetest |
Hi @BartNetJS ! Thanks for your data and your report! I'll use them to simulate this problem and as soon as we have an idea on what I'll return here! |
Thanks @danielbdias, in the mean time i'm looking for a work around. |
Hey @BartNetJS I'll investigate these issues you are experiencing.
When you deleted the release, was the database also deleted? The provisioning only happens in a clean database. If the database is reused, the server will not create the datastore and other structures for you at startup. If you want to reuse the same database, you only need to delete the row in the About the |
We released a new version yesterday and the |
Are you trying to install Tracetest using a new database or an existing one? Would be nice to know, so we can know if that's a bug or a possible feature request. |
@mathnogueira I removed tracetest and the database.
With values.yaml:
Also the release looks ok: |
This is my yaml snipped to provision tracetest:
After install the datastore is not provisioned:
The text was updated successfully, but these errors were encountered: