perconapgbackup could stale forever in Starting
General
Escalation
General
Escalation
Description
AFFECTED CS IDs
CS0050549
Attachments
2
Activity
Show:
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:
Slava Sarzhan November 4, 2024 at 2:07 PM
can you reproduce it with PGO 2.5.0?
Details
Assignee
UnassignedUnassignedReporter
Nickolay IhalainenNickolay Ihalainen(Deactivated)Priority
MediumNeeds QA
YesAffects versions
Details
Details
Assignee
Unassigned
UnassignedReporter
Nickolay IhalainenPriority
MediumNeeds QA
Yes
Affects versions
Smart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Created November 1, 2024 at 2:42 PM
Updated November 8, 2024 at 5:19 PM
It’s unclear why on a production system there are 4d23h
I can’t reproduce why the Job wasn’t created, but could simulate the behavior with:
It leads to infinite stream of messages:
The expected behavior: the operator should have a “timeout” for creating the job and re-try with job creation instead of infinite waiting for backup to start messages.