Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Node leaves cluster when tying to grant table specific permissions to user

Description

DESCRIPTION

When I tries to create new user with table specific privileges or change the existing user - applier thread exists. And this node can't connect back to cluster until I remove user from user tables. Database specific privileges works fine. Log from node attached.

How to reproduce this issue? Just execute following query on any node:

CREATE DATABASE my-database;
CREATE TABLE my-database.tablenamefoo (id int);
CREATE USER 'user'@'%' IDENTIFIED BY 'foobarbaz';
GRANT INSERT, UPDATE, DELETE ON my-database.tablenamefoo TO 'user'@'%';

This way you can stop entire cluster if execute such request on each node.

This bug also posted to Codership at github. They make tests and said that it’s related to PXC - not to Galera Cluster plugin:

Also this bug affected another users:

Environment

--- SOFTWARE VERSIONS ---

MySQL with Galera Cluster
Server: Bazis MySQL Cluster DEV (192.168.254.253 via TCP/IP)
Server type: Percona Server
Server connection: SSL is not being used Documentation
Server version: 8.0.36-28.1 - Percona XtraDB Cluster (GPL), Release rel28, Revision bfb687f, WSREP version 26.1.4.3
Protocol version: 10
User: ZiX@192.168.155.209
Server charset: UTF-8 Unicode (utf8mb3)

Operating System
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy

--- CONFIGURATION ---

3 MySQL nodes on Ubuntu Server 22.04.
Configuration files from one node in attachments:
my.cnf
mysqld.cnf
my.cnf.txt
mysqld.cnf.txt

--- LOGS ---

Logs from node after leaving cluster
mysqld.log
mysqld.log

--- STEPS TO REPRODUCE ---

  1. Create new or select existing user.

  2. Try to grant table specific privileges, for ex. only SELECT for few colums.

--- RESULT ---

#1047 - WSREP has not yet prepared node for application use

Activity

Show:

Kamil Holubicki November 27, 2024 at 9:40 AM

Hello , Thank you for your report. However, we are not able to reproduce it. Please provide a way to reproduce that do not use Cluster Control tool. Maybe this tool does some things not allowed by PXC?

Aaditya Dubey November 21, 2024 at 8:40 AM
Edited

Hi

Since the Cluster Control tool is not our supported tool, there is no point in repeating the issue there; please try repeating the issue outside Cluster Control and share the steps with us to debug the issue further.

As per our colleague :

You might also want to reach out to the makers of CC and see what they say.

Alexey Pletnev November 21, 2024 at 8:19 AM

I have two clusters - one of 3 nodes and one of 5. Both have this issue. I’ve deployed it using Cluster Control tool from SeveralNines (severalnines.com). I can create one more cluster and it also will have same issue.

Will it help if I give you access via ssh to my testing environment?

Aaditya Dubey November 20, 2024 at 12:10 PM

Hi

Thank you for the report.
Unfortunately, I’m unable to repeat the behaviour from my end.
Please share a complete reproducible test case to debug the issue further.

Cannot Reproduce

Assignee

Reporter

Upstream Bug URL

Needs QA

Affects versions

Priority

Created November 20, 2024 at 7:16 AM
Updated November 27, 2024 at 9:50 AM
Resolved November 27, 2024 at 9:40 AM