queue_poison_pill table missing primary key

[ckshen8]

Preconditions and environment

This is the same issue as #33822 , that was originally raised by @sych74, commented by @siliconalchemy and looked into by @engcom-Echo and was closed without resolution.

• Magento version: 2.4.7p2
• Ubuntu 24.04
• MySQL Galera Percona XtraDB 8.0
• PHP 8.3

Steps to reproduce

Prepare database:

mysql -u root -p
CREATE DATABASE magentodb;
CREATE USER 'magento'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password';
GRANT ALL ON `magentodb`.* TO 'magento'@'localhost';
CREATE USER 'magento'@'%' IDENTIFIED WITH mysql_native_password BY 'password';
GRANT ALL ON `magentodb`.* TO 'magento'@'%';
EXIT

Install Magento prequisites- database, PHP, Composer, RabbitMQ, Redis, Elasticsearch

Download Magento Community repository:

composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition=2.4.7-p2 /var/www/html/magento

Set permissions:

cd /var/www/html/magento
find . -type f -exec chmod 644 {} \;            
find . -type d -exec chmod 755 {} \;        
chmod -Rf 777 var
chmod -Rf 777 pub/static
chmod -Rf 777 pub/media
chmod 777 ./app/etc
chmod 644 ./app/etc/*.xml
chmod -Rf 775 bin

Install Magento
php bin/magento setup:install --base-url=<url> --db-host=ip:port --db-name=magentodb --db-user="magento" --db-password=<db password> --admin-firstname="xx" --admin-lastname="yy" --admin-email="xxyy@abc.com" --admin-user="xxyy@abc.com" --admin-password="Testing123%567" --use-rewrites=1 --backend-frontname="admin" --db-prefix=mage_ --timezone=America/Los_Angeles --currency=USD --language=en_US --session-save="redis" --search-engine=elasticsearch8 --elasticsearch-host=<ip> --elasticsearch-port=9200 --elasticsearch-index-prefix=magento2 --amqp-host=<ip> --amqp-port="5672" --amqp-user="magentorabbit" --amqp-password="<magentorabbit password>" --amqp-virtualhost="magento" --amqp-ssl=

Expected result

Magento installed successfully.

Actual result

Magento not installed successfully.

[Progress: 585 / 1448]
Module 'Magento_MessageQueue':
Running schema recurring...
In Mysql.php line 109:
                                                                                                                                                                                       
  SQLSTATE[HY000]: General error: 1105 Percona-XtraDB-Cluster prohibits use of DML command on a table (magentodb.mage_queue_poison_pill) without an explicit primary key with pxc_str  
  ict_mode = ENFORCING or MASTER, query was: INSERT INTO `mage_queue_poison_pill` (`version`) VALUES (?)                                                                               
                                                                                                                                                                                       

In Mysql.php line 90:
                                                                                                                                                                                       
  SQLSTATE[HY000]: General error: 1105 Percona-XtraDB-Cluster prohibits use of DML command on a table (magentodb.mage_queue_poison_pill) without an explicit primary key with pxc_str  
  ict_mode = ENFORCING or MASTER                                                                                                                                                       

Additional information

pxc_strict_mode of the Galera cluster is set to ENFORCING

Per Percona's detailed explanation, the solution is to have primary keys on every table, including queue_poison_pill.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @ckshen8. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Hotel. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Hotel]

Hello @ckshen8,

Thanks for the report and collaboration!

We have checked the documentation linked here related to Percone XtraDB cluster, according to it:

All tables must have a primary key.

This ensures that the same rows appear in the same order on different nodes. The DELETE statement is not supported on tables without a primary key.

And below is the screenshot of the queue_poison_pill table:

which shows that the primary key is missing from the table. Hence confirming the issue.

Thanks