Skip to content

Conversation

@weshayutin
Copy link
Contributor

Why the changes were made

For a higher percentage pass rate, use deployments and not deploymentConfigs for mysql

  • deploymentConfig is now convered by parks-app and downstream

How to test the changes made

via prow is probably fine :)

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 27, 2025
@kaovilai
Copy link
Member

heh..

@kaovilai
Copy link
Member

something

time="2025-10-27T23:46:28Z" level=info msg="Maintenance repo complete, succeeded 0, failed 1" backupRepo=openshift-adp/mysql-persistent-ts-velero-test-1-kopia job name=repo-maintain-job-1761608775907 logSource="pkg/repository/maintenance/maintenance.go:323"
time="2025-10-27T23:46:28Z" level=warning msg="Pruning repository failed" backupRepo=openshift-adp/mysql-persistent-ts-velero-test-1-kopia error="<nil>" logSource="pkg/controller/backup_repository_controller.go:507"
time="2025-10-27T23:46:28Z" level=error msg="Reconciler error" BackupRepository="{\"name\":\"mysql-persistent-ts-velero-test-1-kopia\",\"namespace\":\"openshift-adp\"}" controller=backuprepository controllerGroup=velero.io controllerKind=BackupRepository error="error check and run repo maintenance jobs: error patching BackupRepository: backuprepositories.velero.io \"mysql-persistent-ts-velero-test-1-kopia\" not found" error.file="/go/src/github.com/vmware-tanzu/velero/pkg/controller/backup_repository_controller.go:591" error.function="github.com/vmware-tanzu/velero/pkg/controller.(*BackupRepoReconciler).patchBackupRepository" logSource="/opt/app-root/pkg/mod/github.com/bombsimon/logrusr/v3@v3.0.0/logrusr.go:123" name=mysql-persistent-ts-velero-test-1-kopia namespace=openshift-adp reconcileID="\"a5b714ca-f2c2-4d87-b381-11b48a344d1a\""

@kaovilai
Copy link
Member

time="2025-10-27T23:48:40Z" level=info msg="Set maintenance according to repository suggestion" frequency=1h0m0s logSource="pkg/controller/backup_repository_controller.go:372"
time="2025-10-27T23:48:40Z" level=debug msg="Start to prepare repo" BSL name=ts-velero-test-1 logSource="pkg/repository/provider/unified_repo.go:171" repo UID=7300c4e6-74f6-4b72-a274-310fadb8c98f repo name=mongo-persistent-ts-velero-test-1-kopia
time="2025-10-27T23:48:41Z" level=warning msg="failed to open repository: error loading config file: open /home/velero/udmrepo/repo-7300c4e6-74f6-4b72-a274-310fadb8c98f.conf: no such file or directory" logModule=kopia/kopia/repo logSource="pkg/kopia/kopia_log.go:101" sublevel=error

@kaovilai
Copy link
Member

kaovilai commented Nov 7, 2025

/retest

@kaovilai
Copy link
Member

kaovilai commented Nov 7, 2025

/retest

ai-retester: The e2e-test-cli-aws test failed because the MySQL application KOPIA via CLI test timed out after 540 seconds due to Pods not achieving a "Ready" state, causing failures in the pre-restore steps. Essentially, the Pods were slow to start, exceeding the allotted time.

@kaovilai
Copy link
Member

kaovilai commented Nov 7, 2025

/retest

ai-retester: The e2e-test-aws pod failed because the Parks application Native-Snapshots test had a context deadline exceeded error, failing to complete a restore hook. The underlying problem might be related to the BackupStorageLocation being unavailable.

The e2e-test-cli-aws-e2e step failed because the Mongo application DATAMOVER via CLI test timed out after 540 seconds, indicating a problem with the backup/restore process. The Todolist pod kept initializing but failing.

@kaovilai
Copy link
Member

kaovilai commented Nov 7, 2025

/retest

ai-retester: The e2e test failed because the MySQL application two Vol CSI test timed out waiting for the todolist container in the pod to start, indicated by the error container "todolist" in pod "todolist-c8b9b9565-9l2js" is waiting to start: PodInitializing.

@openshift-ci
Copy link

openshift-ci bot commented Nov 8, 2025

@weshayutin: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-ci
Copy link

openshift-ci bot commented Nov 8, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kaovilai, weshayutin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants