pxc upgrade error: update error: Operation cannot be fulfilled on statefulsets.apps \"db-pxc\": the object has been modified; please apply your changes to the latest version and try again

Description

Hi,

I have created a PXC Cluster with 3 Nodes using the K8S Operator. It was created using version 1.5.0 of the Operator. The cluster sometimes crashes and is not able to fully recover. In the logs of the operator I can see the following errors:

Updating to 1.6.0 and 1.7.0 did not help. I tried to delete the Statefulset, it automatically gets created again by the Operator and the error persists. Otherwise the cluster runs fine. Any clues?

Environment

  • Kubernetes Version: v1.18.8

  • Cluster created with Rancher v2.5.2

  • Provider: Hetzner Cloud

  • Nodes running Docker 19.3.11

  • OS: Ubuntu 20.04 LTS 5.4.0-33-generic

Attachments

1

Smart Checklist

Activity

Jira Bot August 29, 2021 at 11:57 AM

Hello ,
It's been 52 days since this issue went into Incomplete and we haven't heard
from you on this.

At this point, our policy is to Close this issue, to keep things from getting
too cluttered. If you have more information about this issue and wish to
reopen it, please reply with a comment containing "jira-bot=reopen".

Jira Bot August 21, 2021 at 11:56 AM

Hello ,
It's jira-bot again. Your bug report is important to us, but we haven't heard
from you since the previous notification. If we don't hear from you on
this in 7 days, the issue will be automatically closed.

Jira Bot August 6, 2021 at 10:57 AM

Hello ,
I'm jira-bot, Percona's automated helper script. Your bug report is important
to us but we've been unable to reproduce it, and asked you for more
information. If we haven't heard from you on this in 3 more weeks, the issue
will be automatically closed.

Lalit Choudhary July 8, 2021 at 10:53 AM

Hi

Thank you for the details.
[ERROR] WSREP: handshake with remote endpoint ssl:/
The ssl issue bit different can cause due missing ssl file or wrong ssl files/details.

This issue occurs even on a new K8S cluster created with Rancher.
 
Kubernetes Version: v1.19.7

 

Can you help us with full steps to reproduciable this issue with test case ?

 

Thomas Biela May 18, 2021 at 1:06 PM

This issue occurs even on a new K8S cluster created with Rancher.
 
Kubernetes Version: v1.19.7

Incomplete

Details

Assignee

Reporter

Affects versions

Priority

Smart Checklist

Created February 8, 2021 at 4:40 PM
Updated March 5, 2024 at 5:57 PM
Resolved August 29, 2021 at 11:57 AM