Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.5.5
Description
A user that had REPLICATION SLAVE, REPLICATION CLIENT privileges before upgrade to 10.5, has REPLICATION SLAVE, BINLOG MONITOR after upgrade, but is not able to run SHOW SLAVE STATUS anymore, as it is missing the new REPLICATION SLAVE ADMIN privilege now which is necessary for this in 10.5.
IMHO mysql_upgrade should take care of replacing REPLICATION CLIENT with BINLOG MONITOR, REPLICATION SLAVE ADMIN when doing a pre-10.5 to 10.5 or later upgrade.
Same for REPLICATION SLAVE, that should become REPLICATION SLAVE, REPLICATION MASTER ADMIN, REPLICATION SLAVE ADMIN instead on upgrades to 10.5., so that existing users can still continue to use SHOW SLAVE HOSTS and SHOW RELAYLOG EVENTS.
Attachments
Issue Links
- duplicates
-
MDEV-23899 admin privilege required to monitoring replication status - 10.5.5
- Closed
- is caused by
-
MDEV-21743 Split up SUPER privilege to smaller privileges
- Closed
- relates to
-
MDEV-22030 Don't grant REPLICATION MASTER ADMIN automatically on upgrade from an older JSON user table
- Closed
-
MDEV-22152 REPLICATION MASTER ADMIN privilege not given to former SUPER users upon upgrade
- Closed
-
MDEV-23918 admin privlege required to view contents of relay logs in 10.5
- Closed