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
Database barclamp proposal failed with error "Access denied for user 'db_maker@192.168.124.xx'" #2015
Comments
It's related to https://github.com/crowbar/barclamp-mysql or https://github.com/crowbar/barclamp-database. And I'm not sure if there will come any bugfixes for the quite old version betty. Current legacy version is hydrogen, mostly stable on SLES is roxy and under heavy development is stoney. |
Hi Thomas, Can you point me to a stable version of crowbar, since I checked the site and it does point to a dead location for the most recent version of crowbar. Thanks Regards, From: Thomas Boerger [mailto:notifications@github.com] It's related to https://github.com/crowbar/barclamp-mysql or https://github.com/crowbar/barclamp-database. And I'm not sure if there will come any bugfixes for the quite old version betty. Current legacy version is hydrogen, mostly stable on SLES is roxy and under heavy development is stoney. — |
hgaikwad , From: hgaikwad [mailto:notifications@github.com] Description: Version/Build: betty_openstack-os-build.2561.dev Browsers Used: IE11.0 Reproduction Steps:
Observed Results: Expected Results: Impact: — |
Arkady, Regards, |
Description:
Database barclamp proposal failed with error "Access denied for user 'db_maker@192.168.124.xx'"
Version/Build: betty_openstack-os-build.2561.dev
Browsers Used: IE11.0
Reproduction Steps:
Observed Results:
Database barclamp proposal failed with error "Access denied for user 'db_maker@192.168.124.xx'"
Expected Results:
Proposal to be applied successfully without any failure
Impact:
MySQL barclamp being the base barclamp based on which all other barclamps are dependent, the failure actually blocks the entire OpenStack deployment.
The text was updated successfully, but these errors were encountered: