Skip to content

Conversation

@egegunes
Copy link
Contributor

@egegunes egegunes commented May 14, 2025

K8SPXC-1647 Powered by Pull Request Badge

CHANGE DESCRIPTION

Problem:
Short explanation of the problem.

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

Solution:
Short explanation of the solution we are providing with this PR.

TODO:

  • garbd says /* Reserved 99 exit codes. recv-script should use exit codes 0 or > GARBD_EXIT_CODE_LAST*/. We need to use exit codes >200 if we have any failure in recv script that we want to distinguish.
  • If you kill the donor while files are being received from Donor and streamed to storage, recv script exits with 0. We need to address this in recv script.

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?

@pull-request-size pull-request-size bot added the size/M 30-99 lines label May 14, 2025
Comment on lines +76 to +95
0)
log 'INFO' 'Backup was finished successfully'
exit 0
;;
100)
log 'ERROR' 'Backup was unsuccessful: Generic failure'
exit 1
;;
101)
log 'ERROR' 'Backup was unsuccessful: Donor disappeared'
exit 1
;;
102)
log 'ERROR' 'Backup was unsuccessful: SST request failure'
exit 1
;;
*)
log 'ERROR' "Backup was unsuccessful: garbd exited with ${GARBD_EXIT_CODE}"
exit 1
;;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[shfmt] reported by reviewdog 🐶

Suggested change
0)
log 'INFO' 'Backup was finished successfully'
exit 0
;;
100)
log 'ERROR' 'Backup was unsuccessful: Generic failure'
exit 1
;;
101)
log 'ERROR' 'Backup was unsuccessful: Donor disappeared'
exit 1
;;
102)
log 'ERROR' 'Backup was unsuccessful: SST request failure'
exit 1
;;
*)
log 'ERROR' "Backup was unsuccessful: garbd exited with ${GARBD_EXIT_CODE}"
exit 1
;;
0)
log 'INFO' 'Backup was finished successfully'
exit 0
;;
100)
log 'ERROR' 'Backup was unsuccessful: Generic failure'
exit 1
;;
101)
log 'ERROR' 'Backup was unsuccessful: Donor disappeared'
exit 1
;;
102)
log 'ERROR' 'Backup was unsuccessful: SST request failure'
exit 1
;;
*)
log 'ERROR' "Backup was unsuccessful: garbd exited with ${GARBD_EXIT_CODE}"
exit 1
;;

@pull-request-size pull-request-size bot added size/L 100-499 lines and removed size/M 30-99 lines labels May 19, 2025
Comment on lines +65 to +72
--address "gcomm://$NODE_NAME.$PXC_SERVICE?gmcast.listen_addr=tcp://0.0.0.0:4567" \
--donor "$NODE_NAME" \
--group "$PXC_SERVICE" \
--options "$GARBD_OPTS" \
--sst "xtrabackup-v2:$LOCAL_IP:4444/xtrabackup_sst//1" \
--extended-exit-codes \
--wait-for-recv-script-exit \
--recv-script="/opt/percona/backup/run_backup.sh"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[shfmt] reported by reviewdog 🐶

Suggested change
--address "gcomm://$NODE_NAME.$PXC_SERVICE?gmcast.listen_addr=tcp://0.0.0.0:4567" \
--donor "$NODE_NAME" \
--group "$PXC_SERVICE" \
--options "$GARBD_OPTS" \
--sst "xtrabackup-v2:$LOCAL_IP:4444/xtrabackup_sst//1" \
--extended-exit-codes \
--wait-for-recv-script-exit \
--recv-script="/opt/percona/backup/run_backup.sh"
--address "gcomm://$NODE_NAME.$PXC_SERVICE?gmcast.listen_addr=tcp://0.0.0.0:4567" \
--donor "$NODE_NAME" \
--group "$PXC_SERVICE" \
--options "$GARBD_OPTS" \
--sst "xtrabackup-v2:$LOCAL_IP:4444/xtrabackup_sst//1" \
--extended-exit-codes \
--wait-for-recv-script-exit \
--recv-script="/opt/percona/backup/run_backup.sh"

--parallel="$(grep -c processor /proc/cpuinfo)" \
$XBCLOUD_ARGS \
"$BACKUP_PATH" 2>&1 \
| (grep -v "error: http request failed: Couldn't resolve host name" || exit 1) &
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[shfmt] reported by reviewdog 🐶

Suggested change
| (grep -v "error: http request failed: Couldn't resolve host name" || exit 1) &
| (grep -v "error: http request failed: Couldn't resolve host name" || exit 1) &

@JNKPercona
Copy link
Collaborator

Test Name Result Time
affinity-8-0 failure 00:00:00
auto-tuning-8-0 passed 00:16:48
cross-site-8-0 passed 00:31:37
custom-users-8-0 failure 00:00:00
demand-backup-cloud-8-0 passed 00:53:25
demand-backup-encrypted-with-tls-8-0 passed 00:42:52
demand-backup-8-0 failure 00:29:44
demand-backup-flow-control-8-0 passed 00:10:34
demand-backup-parallel-8-0 failure 00:00:00
demand-backup-without-passwords-8-0 failure 00:30:54
haproxy-5-7 passed 00:12:53
haproxy-8-0 passed 00:12:44
init-deploy-5-7 failure 00:16:55
init-deploy-8-0 passed 00:17:43
limits-8-0 failure 00:10:44
monitoring-2-0-8-0 failure 00:09:00
monitoring-pmm3-8-0 passed 01:23:30
one-pod-5-7 failure 00:03:24
one-pod-8-0 failure 00:03:18
pitr-8-0 passed 00:42:59
pitr-gap-errors-8-0 passed 00:52:26
proxy-protocol-8-0 failure 00:08:31
proxysql-sidecar-res-limits-8-0 passed 00:08:16
pvc-resize-5-7 passed 00:13:21
pvc-resize-8-0 passed 00:14:50
recreate-8-0 passed 00:16:23
restore-to-encrypted-cluster-8-0 passed 00:23:42
scaling-proxysql-8-0 passed 00:07:42
scaling-8-0 passed 00:09:51
scheduled-backup-5-7 failure 00:27:29
scheduled-backup-8-0 failure 00:59:13
security-context-8-0 passed 00:24:30
smart-update1-8-0 passed 00:37:19
smart-update2-8-0 passed 00:35:04
storage-8-0 failure 00:09:14
tls-issue-cert-manager-ref-8-0 passed 00:07:48
tls-issue-cert-manager-8-0 passed 00:10:38
tls-issue-self-8-0 passed 00:12:42
upgrade-consistency-8-0 passed 00:10:34
upgrade-haproxy-5-7 failure 00:20:05
upgrade-haproxy-8-0 passed 00:23:06
upgrade-proxysql-5-7 passed 00:13:33
upgrade-proxysql-8-0 passed 00:16:35
users-5-7 failure 00:00:50
users-8-0 failure 00:00:46
validation-hook-8-0 passed 00:01:40
We run 46 out of 46 14:55:32

commit: e995968
image: perconalab/percona-xtradb-cluster-operator:PR-2076-e9959688

@hors hors added this to the v1.19.0 milestone Jul 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/L 100-499 lines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants