Skip to:

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

Description

None

Environment

None

AFFECTED CS IDs

CS0050549

Activity

Nickolay Ihalainen November 8, 2024 at 5:19 PM

yes, I was able to fully reproduce the case, but want to keep this issue just for log messages spam: https://perconadev.atlassian.net/browse/K8SPG-680

 

$ kubectl -n pgo logs percona-postgresql-operator-6547b6774c-j9zfb |grep -c 'Waiting for backup to start' 226 $ kubectl -n pgo logs percona-postgresql-operator-6547b6774c-j9zfb |grep -m 1 'Waiting for backup to start' 2024-11-08T17:00:04.034Z INFO Waiting for backup to start {"controller": "perconapgbackup", "controllerGroup": "pgv2.percona.com", "controllerKind": "PerconaPGBackup", "PerconaPGBackup": {"name":"cluster1-repo1-full-qvv9r","namespace":"pgo"}, "namespace": "pgo", "name": "cluster1-repo1-full-qvv9r", "reconcileID": "44fcb781-fd0f-4bc1-afbb-76c3a231e65d", "request": {"name":"cluster1-repo1-full-qvv9r","namespace":"pgo"}} $ kubectl -n pgo logs percona-postgresql-operator-6547b6774c-j9zfb |tail -n 1 2024-11-08T17:19:14.266Z INFO Waiting for backup to start {"controller": "perconapgbackup", "controllerGroup": "pgv2.percona.com", "controllerKind": "PerconaPGBackup", "PerconaPGBackup": {"name":"cluster1-repo1-full-qvv9r","namespace":"pgo"}, "namespace": "pgo", "name": "cluster1-repo1-full-qvv9r", "reconcileID": "489b5d65-5ec6-4c09-94bc-2fc1d858193e", "request": {"name":"cluster1-repo1-full-qvv9r","namespace":"pgo"}}

Slava Sarzhan November 4, 2024 at 2:07 PM

can you reproduce it with PGO 2.5.0?

Something went wrong on our end

If this keeps happening, share this information with your admin, who should contact support.

Hash 1JOJMU2 Trace f4744ed1a6254eca96f0ad6d7b3fe7d9

Details

Assignee

Unassigned

Reporter

Nickolay Ihalainen(Deactivated)

Needs QA

Yes

Smart Checklist

Flag notifications