DBaaS: PXC cluster is displayed as active after suspend

General

Escalation

General

Escalation

Description

User impact:

PXC cluster is displayed as ACTIVE after user pauses it and cannot be resumed in UI

Steps to reproduce:

Install PMM 2.23.0 RC
Create a PXC cluster
Click Suspend once it's ready

Actual result:

Pods are deleted and the cluster is listed as active in UI

Before:

qa@qa:~$ kubectl get pods
NAME READY STATUS RESTARTS AGE
percona-server-mongodb-operator-7ff49bcf85-gwpk5 1/1 Running 0 18h
percona-xtradb-cluster-operator-79966668bd-7hrnd 1/1 Running 0 18h
sus-haproxy-0 1/2 Running 0 22s
sus-pxc-0 1/2 Running 0 22s

After suspend:

qa@qa:~$ kubectl get pods
NAME READY STATUS RESTARTS AGE
f564c-test-1633680000-s58q9 0/1 Completed 0 2m54s
percona-server-mongodb-operator-7ff49bcf85-gwpk5 1/1 Running 0 18h
percona-xtradb-cluster-operator-79966668bd-7hrnd 1/1 Running 0 18h

Expected result:

Cluster PAUSED

Workaround:

Details:

How to test

None

How to document

None

FB test

None

Attachments

3.136.25.124_Archive [21-10-08 10-02-45].har

11 Oct, 2021

image-2021-10-08-10-05-27-330.png

08 Oct, 2021

Activity

Former user

October 18, 2021 at 9:17 AM

tests are timing out, need to figure this out, +0.5 story point

Resize work item view side panel

Done

Details

Assignee

Unassigned

Reporter

Former user(Deactivated)

Priority

Critical

Components

DBaaS controller

Labels

defect

Needs QA

Yes

Fix versions

2.23.0

Story Points

2.5

Regression Issue

Yes

Affects versions

2.23.0

Created October 8, 2021 at 7:49 AM

Updated January 2, 2023 at 1:24 PM

Resolved October 19, 2021 at 11:13 AM