Skip to content

Conversation

@eleo007
Copy link
Contributor

@eleo007 eleo007 commented Sep 21, 2025

K8SPXC-1719 Powered by Pull Request Badge

CHANGE DESCRIPTION

Problem:
During install of chaos mesh runtime should be specified. We have used default containerd for all the platforms while openshift uses cri-o and minkube uses docker.

Cause:
Short explanation of the root cause of the issue if applicable.

Solution:
Check node rntime before install of chaos mesh.

CHECKLIST

Jira

  • Is the Jira ticket created and referenced properly?
  • Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
  • Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

  • Is an E2E test/test case added for the new feature/change?
  • Are unit tests added where appropriate?
  • Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

Config/Logging/Testability

  • Are all needed new/changed options added to default YAML files?
  • Are all needed new/changed options added to the Helm Chart?
  • Did we add proper logging messages for operator actions?
  • Did we ensure compatibility with the previous version or cluster upgrade process?
  • Does the change support oldest and newest supported PXC version?
  • Does the change support oldest and newest supported Kubernetes version?

@eleo007 eleo007 force-pushed the K8SPXC-1719-fix-chaos branch from 26d0db4 to a892b00 Compare September 21, 2025 20:47
@JNKPercona
Copy link
Collaborator

Test Name Result Time
auto-tuning-8-0 passed 00:18:56
allocator-8-0 passed 00:12:36
backup-storage-tls-8-0 passed 00:22:28
cross-site-8-0 passed 00:34:48
custom-users-8-0 passed 00:12:04
demand-backup-cloud-8-0 passed 00:57:10
demand-backup-encrypted-with-tls-8-0 passed 00:45:19
demand-backup-8-0 passed 00:41:10
demand-backup-flow-control-8-0 passed 00:10:37
demand-backup-parallel-8-0 passed 00:08:56
demand-backup-without-passwords-8-0 passed 00:15:38
haproxy-5-7 passed 00:13:13
haproxy-8-0 passed 00:14:42
init-deploy-5-7 passed 00:16:27
init-deploy-8-0 passed 00:16:53
limits-8-0 passed 00:12:13
monitoring-2-0-8-0 passed 00:22:35
monitoring-pmm3-8-0 passed 00:18:05
one-pod-5-7 passed 00:13:54
one-pod-8-0 passed 00:13:16
pitr-8-0 passed 00:43:55
pitr-gap-errors-8-0 passed 00:57:01
proxy-protocol-8-0 passed 00:09:27
proxy-switch-8-0 passed 00:13:03
proxysql-sidecar-res-limits-8-0 passed 00:08:23
proxysql-scheduler-8-0 passed 00:15:51
pvc-resize-5-7 passed 00:14:46
pvc-resize-8-0 passed 00:16:45
recreate-8-0 passed 00:17:13
restore-to-encrypted-cluster-8-0 passed 00:25:16
scaling-proxysql-8-0 passed 00:08:30
scaling-8-0 passed 00:10:53
scheduled-backup-5-7 passed 01:03:42
scheduled-backup-8-0 passed 01:02:54
security-context-8-0 passed 00:26:09
smart-update1-8-0 passed 00:32:47
smart-update2-8-0 passed 00:38:13
storage-8-0 passed 00:10:40
tls-issue-cert-manager-ref-8-0 passed 00:08:35
tls-issue-cert-manager-8-0 passed 00:09:37
tls-issue-self-8-0 passed 00:13:03
upgrade-consistency-8-0 passed 00:11:20
upgrade-haproxy-5-7 passed 00:24:04
upgrade-haproxy-8-0 passed 00:24:21
upgrade-proxysql-5-7 passed 00:14:23
upgrade-proxysql-8-0 passed 00:14:07
users-5-7 passed 00:24:52
users-8-0 passed 00:26:50
validation-hook-8-0 passed 00:01:57
Summary Value
Tests Run 49/49
Job Duration 02:52:00
Total Test Time 17:50:04

commit: 1eb37b2
image: perconalab/percona-xtradb-cluster-operator:PR-2193-1eb37b20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/M 30-99 lines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants