pxc-db helm chart has wrong PXC version for 1.14.0 release

Description

If automatic upgrade is enabled on each helm chart upgrade it tries to downgrade the database: https://forums.percona.com/t/using-pxc-db-helm-chart-with-smartupdate/29193

We need to see if it is possible to fix this somehow.

Environment

None

Activity

Show:

Tomislav Plavcic March 18, 2024 at 12:41 PM

The fix is now merged. Thanks again!

Tomislav Plavcic March 18, 2024 at 12:24 PM

Ah I see now, this was actually an error while updating things for 1.14.0 release. Usually we set it like this, but it was missed this time.

I have a PR here and will merge it today: https://github.com/percona/percona-helm-charts/pull/307

You have some interesting ideas for fixes, but for now let’s not complicate so we will just fix the version and in the future if this will not work we will think about other fixes.

Thank you very much for quick response!

Paweł Rosada March 18, 2024 at 11:53 AM

Hello

We have been discussing an issue internally and believe that the optimal solution would involve incrementing the version numbers for various components such as PXC, PMM, ProxySQL, HAProxy, etc., each time a new chart version is released. For instance, in the case of PXC, the currently available versions are as follows:

"8.0.25-15.1": { "imagePath": "percona/percona-xtradb-cluster:8.0.25-15.1", "imageHash": "529e979c86442429e6feabef9a2d9fc362f4626146f208fbfac704e145a492dd", "imageHashArm64": "", "status": "available", "critical": false }, "8.0.29-21.1": { "imagePath": "percona/percona-xtradb-cluster:8.0.29-21.1", "imageHash": "96c6bb8189280aeb773e74ed46aa41c01781b62947ed70c89efeb9f41c367ee7", "imageHashArm64": "", "status": "available", "critical": false }, "8.0.31-23.2": { "imagePath": "percona/percona-xtradb-cluster:8.0.31-23.2", "imageHash": "e47110307e9733fbcc55e5587652e41bbcf794063b021533d5e705062da97927", "imageHashArm64": "", "status": "available", "critical": false }, "8.0.32-24.2": { "imagePath": "percona/percona-xtradb-cluster:8.0.32-24.2", "imageHash": "1f978ab8912e1b5fc66570529cb7e7a4ec6a38adbfce1ece78159b0fcfa7d47a", "imageHashArm64": "", "status": "available", "critical": false }, "8.0.35-27.1": { "imagePath": "percona/percona-xtradb-cluster:8.0.35-27.1", "imageHash": "1ef24953591ef1c1ce39576843d5615d4060fd09458c7a39ebc3e2eda7ef486b", "imageHashArm64": "", "status": "recommended", "critical": false }

However, it seems that the default version is set to 8.0.32-24.2, which might indicate that it was not updated to the latest recommended version, 8.0.35-27.1. In Helm, I am looking for options to address this issue, but it appears to be quite complex. One potential solution might involve using a postrender option to retrieve the version from the PXC deployment.

After reviewing the situation, I believe that the best course of action would be to automatically set the default version in the Helm configuration to the latest available version

Done

Details

Assignee

Reporter

Labels

Needs QA

Yes

Components

Fix versions

Affects versions

Priority

Smart Checklist

Created March 18, 2024 at 10:45 AM
Updated March 18, 2024 at 12:42 PM
Resolved March 18, 2024 at 12:41 PM