MySQL Bugs: #108189: MySQL Enterprise Operator 8.0.30-2.0.5 (Patch: 34422216) Shell Version Issue

Bug #108189	MySQL Enterprise Operator 8.0.30-2.0.5 (Patch: 34422216) Shell Version Issue
Submitted:	18 Aug 2022 11:11	Modified:	13 Sep 2022 8:46
Reporter:	Avash Kumar	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Operator	Severity:	S1 (Critical)
Version:	8.0.30-2.0.5	OS:	Linux (RHEL 8)
Assigned to:		CPU Architecture:	x86

Description:
MySQL Enterprise Operator version 8.0.30-2.0.5 (Patch Number 34422216) installs with mysql shell version 8.0.29 & runs the same version as sidecar to mysql enterprise server . This causes iptables issue while creating innodb cluster with mysql server 8.0.30
However the community edition of MySQL Operator v8.0.30-2.0.5 installs with shell version 8.0.30 & is able to create innodb cluster with enterprise server v8.0.30

How to repeat:
[case 1]
Install mysql enterprise operator v8.0.30-2.0.5 (Patch 34422216) . Create 3 pod Innodb Cluster from Enterprise Server v8.0.30 (Patch 34421881) . This causes IP tables error while one pod tries to communicate to other

[case 2]
Install mysql community operator v8.0.30-2.0.5 (image repo available in mysql operator github) . Create 3 pod Innodb Cluster from Enterprise Server v8.0.30 (Patch 34421881) . This setup works perfectly OK

Suggested fix:
Update the mysql shell version in MySQL Enterprise Operator v8.0.30-2.0.5 from 8.0.29 to 8.0.30 as present in MySQL Community Operator v8.0.30-2.0.5 .
This would fix the iptables issue .

This is as per mentioned in the Realse notes link https://dev.mysql.com/doc/relnotes/mysql-operator/en/news-8-0-30.html

>>> Group replication now uses the MySQL protocol to establish connections instead of the internal XCom communication infrastructure. Newly created clusters use the MySQL Protocol via port 3306, whereas clusters created using a previous version will continue to use XCom on port 33061.

hi Team

As i have recieved info in SR, Dev team is planning to push the Image with corrected version with new tags. 
Is there any ETA for this ?

regards

Posted by developer:
 
Fixed as of the upcoming MySQL Operator 8.0.30-2.0.6 release, and here's the proposed changelog entry from the documentation team:

The 8.0.30 enterprise edition installs MySQL Shell 8.0.29 instead of 8.0.30.

Thank you for the bug report.

Quick update. MySQL Operator 8.0.30-2.0.6 release published now.

Where can i find the published version 8.0.30-2.0.6 for enterprise operator ?

I am unable to view this in container-registry.oracle.com

MySQL Operator 8.0.30-2.0.6 release published on MOS, dev.mysql.com, eDelivery, dockerhub and github. 

We will publish to OCR asap (pending approval).

Do let us know when mysql enterprise operator version 8.0.30-2.0.6 is pushed to OCR .

MySQL Enterprise Operator 8.0.30-2.0.6 is available in the OCR now.

hi 

I tested the MySQL Operator version 8.0.30-2.0.6, 

The issue now is enterprise-operator(v8.0.30-2.0.6) is running with mysql shell version 8.0.31 ,

whereas community-operator(v8.0.30-2.0.6) is running with mysql shell version 8.0.30.

How to reproduce:

1. Run deployments of enterprise-operator(v8.0.30-2.0.6) & community-operator(v8.0.30-2.0.6) 

2. Enter pod & execute command view the version difference
< mysqlsh --version >

CONCERN:

Since enterprise-operator(v8.0.30-2.0.6) supports mysql server(v8.0.30), as customers we would prefer to have similar version of shell & server running.

Also we don't understand the reason behind different 'mysql shell versions' for the same product version in community & enterprise edition

regards

hi 

Is the enterprise operator v8.0.30-2.0.6 currently removed from Oracle Repos ???
Attached is the screnshot for the same.
I don't see it available now currently in OCR or as a Patch Version.
Kindly reupload it on priority basis with appropriate version fixes.

Our prod deployment is stuck for more than 2 weeks due to the same issue.

regards

MySQL Enterprise Operator v8.0.30-2.0.6 currently unavailable in Support Hub

Attachment: MySQL Operator 2.0.6 NA.png (image/png, text), 221.82 KiB.

We have re-published the MySQL Enterprise Operator 8.0.30-2.0.6 images now.

is it tested that it has correct mysql shell version (v8.0.30) installed for enterprise operator (v8.0.30-2.0.6) ?