We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug ucp keystone-db-sync-sn48z is in CrashLoopBackOff due to credential' already exists
Steps To Reproduce Maintain treasurmap version @ 2227df4 and follow the steps to bring up genesis node.
Expected behavior keystone-db-sync pods should be running status.
Environment
Workaround change the version of mariadb_db to be in sync with mariadb_db client and server.
mariadb_db: &mariadb_db docker.io/openstackhelm/mariadb:ubuntu_xenial-20200722
mariadb_db: &mariadb_db docker.io/openstackhelm/mariadb:ubuntu_xenial-20200811
The text was updated successfully, but these errors were encountered:
Issues is addressed with the right version of the image for mariadb_db and tested by the reporter.
Sorry, something went wrong.
No branches or pull requests
Describe the bug
ucp keystone-db-sync-sn48z is in CrashLoopBackOff due to credential' already exists
Steps To Reproduce
Maintain treasurmap version @ 2227df4 and follow the steps to bring up genesis node.
Expected behavior
keystone-db-sync pods should be running status.
Environment
Workaround
change the version of mariadb_db to be in sync with mariadb_db client and server.
The text was updated successfully, but these errors were encountered: