Skip to:

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

Cluster status doesn't show failure in dbaas

Description

User impact:

Cluster Status doesn't show error in UI as before

STR:

Register K8s cluster in dbaas
Make sure that PXC operator 1.9.0 is installed
Create a PXC cluster that will fail due to insufficient cpu or memory

Actual result:

Expected result:

As it used to work in PMM 2.21.0 with percona/percona-xtradb-cluster-operator:1.8.0

How to test

None

How to document

None

Attachments

3

is caused by

Smart Checklist

Activity

Show:

Tiago Mota November 5, 2021 at 10:37 AM

Former user September 17, 2021 at 9:43 AM
Edited

After discussion done in https://perconacorp.slack.com/archives/C01F3TX1CL8/p1631807971019700?thread_ts=1631779063.016900&cid=C01F3TX1CL8, let's just display logs link and the message if the message it's not empty. Or display it always?

Former user September 16, 2021 at 8:07 AM

From https://www.percona.com/blog/cluster-statuses-in-percona-kubernetes-operators/

Before 1.9.0, “error” status could mean two different things:

  1. An error occurred in the operator during the reconciliation of the CR

  2. One or more pods in a component are not schedulable

With 1.9.0, the “error” status means only the operator errors. If there is an unschedulable pod, the cluster’s status will be initializing. If the cluster is stuck in initializing for too long, it’s better to check the operator logs to investigate.

Done

Details

Assignee

Reporter

Priority

Needs QA

Yes

Fix versions

Story Points

Parent

Smart Checklist

Created September 6, 2021 at 9:26 AM
Updated December 18, 2021 at 11:57 AM
Resolved November 12, 2021 at 10:36 AM
Configure