Unexpected behaviour on pitr restore out of range

Description

On pitr restoring if specified wrong time (out of range provided by pbm list), there are at least to different errors may occure.

If error like:
Failed with "no chunk with the target time, the last chunk ends on {1682419209 3}"

We're getting restore info (pbm list --restore --out=json) like following:
*start : 1682421599
status : "error"
type : "pitr"
snapshot : "2023-04-25T10:35:05Z"
point-in-time : 1682420113
name : "2023-04-25T11:19:58.516638545Z"
error : "no chunk with the target time, the last chunk ends on {1682419209 3}"*

But if pbm produces error like following:
Failed with "no backup found before ts {1682418612 0}"

Restore info different:
*start : 1682421860
status : "error"
type : "snapshot"
name : "2023-04-25T11:24:20.285709967Z"
error : "no backup found before ts {1682418612 0}"*

There are different field set in responses and different restore types. That causes problems for us when we're parsing PBM response in PMM.

Environment

None

Activity

Show:

radoslaw.szulgo October 29, 2024 at 12:39 PM

it's working as design - two different errors have two different messages - no plan to fix.

Won't Do

Details

Assignee

Reporter

Labels

Needs QA

Yes

Affects versions

Priority

Smart Checklist

Created April 26, 2023 at 11:56 AM
Updated October 29, 2024 at 12:39 PM
Resolved October 29, 2024 at 12:39 PM