[PR #338/1dcc5ec0 backport][stable-2] mysql_user: added flush privileges to write dynamic privs into db #339
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backport of PR #338 as merged into main (1dcc5ec).
Fixes #120
SUMMARY
Added Flush Privileges after the revoke all privileges to write consitent the dynamic privileges which are required for cluster creation
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION
Without this fix a user with all privileges is only on every second run allowed to create a cluster or replicaset on the host.
Mysqlsh with dba.checkInstanceConfiguration() is failing because these rights are missing:
CLONE_ADMIN, CONNECTION_ADMIN, GROUP_REPLICATION_ADMIN, PERSIST_RO_VARIABLES_ADMIN, REPLICATION_APPLIER, REPLICATION_SLAVE_ADMIN, ROLE_ADMIN, SYSTEM_VARIABLES_ADMIN
After a new run with
priv: "*.*:ALL,GRANT"
the dba.checkInstanceConfiguration() check is successfull.More Details could be found in the issue #120