-
Notifications
You must be signed in to change notification settings - Fork 10
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
fix(entrypoint): continue startup if TLS cert import fails #475
Conversation
/build_test |
Workflow started at 5/23/2024, 3:40:58 PM. View Actions Run. |
No GraphQL schema changes detected. |
No OpenAPI schema changes detected. |
CI build and push: All tests pass ✅ (JDK17) |
b4576a2
to
d3f3836
Compare
/build_test |
Workflow started at 5/30/2024, 11:16:54 AM. View Actions Run. |
No OpenAPI schema changes detected. |
No GraphQL schema changes detected. |
CI build and push: All tests pass ✅ (JDK17) |
d3f3836
to
fcc4032
Compare
/build_test |
Workflow started at 5/30/2024, 1:31:21 PM. View Actions Run. |
No GraphQL schema changes detected. |
No OpenAPI schema changes detected. |
CI build and push: All tests pass ✅ (JDK17) |
58880a2
to
7b23e86
Compare
7b23e86
to
6a9d762
Compare
Welcome to Cryostat3! 👋
Before contributing, make sure you have:
main
branch[chore, ci, docs, feat, fix, test]
To recreate commits with GPG signature
git fetch upstream && git rebase --force --gpg-sign upstream/main
Fixes: #474
See also #462 - if JMX credentials pwfile/usrfile are already created, then the same reproduction steps will also fail because the previous container instance's files are still present but were created by a different container UID and so the new container instance has no access to the existing filesHow to test:
cryostat3/truststore
directory./smoketest.bash -O
podman restart compose_cryostat_1
. Cryostat should successfully restart - before this PR it would repeatedly fail to start due to the TLS cert already having been imported.