cbbackupmgr start and end validations is a bit too aggressive

Description

Problem
In 7.0.0 this command fails where it works on 6.6.0:

This is one of the only cases where having latest or end as the --start is valid. The same is true for --end with oldest or start.

Suggestion

Should validate that the key word is correct, then check that --start is older or the same as --end.

Components

Affects versions

Fix versions

Labels

Environment

None

Link to Log File, atop/blg, CBCollectInfo, Core dump

None

Release Notes Description

None

Activity

Joe Mitchell Jones September 1, 2021 at 12:55 PM

Confirmed this now works when start and end are both latest/oldest. Closing.

CB robot August 23, 2021 at 11:01 AM

Build couchbase-server-7.1.0-1187 contains backup commit baf9dee with commit message:
Relax start/end keyword validation

CB robot August 23, 2021 at 9:20 AM

Build couchbase-server-7.0.2-6565 contains backup commit baf9dee with commit message:
Relax start/end keyword validation

Daniel Owen August 20, 2021 at 5:16 PM

Approved for 7.0.2 by Arunkumar Senthilnathan via email

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Is this a Regression?

Yes

Triage

Triaged

Story Points

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created August 20, 2021 at 4:31 PM
Updated September 1, 2021 at 12:55 PM
Resolved August 23, 2021 at 10:41 AM
Instabug