Bug 2302392 - OADP backup fails when writing to a noobaa bucket backed with LVM storage
Summary: OADP backup fails when writing to a noobaa bucket backed with LVM storage
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: Multi-Cloud Object Gateway
Version: 4.15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Nimrod Becker
QA Contact: krishnaram Karthick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-08-01 21:41 UTC by Brenda McLaren
Modified: 2024-09-16 07:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OCSBZM-8792 0 None None None 2024-08-01 21:41:57 UTC

Description Brenda McLaren 2024-08-01 21:41:11 UTC
Description of problem:

Deployed MCG on SNO cluster using LVM storage and deployed OADP using OBC in noobaa SC.  The backups fail on the dataupload with the message Cancelled.

Deployed dev version of OADP to address the Cancelling of backups but still unable to complete a successful backup using noobaa backed by LVM storage.  Error message received is "409 - bucket in invalid state.


Version of all relevant components (if applicable):

OADP - upstream v99.0
ODF - v4.15.5
LVM - 4.15.5

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

The use case is for one SNO instance to backup VMs to another SNO instance so that in the event of a SNO failure the VMs would be able to be restored to the opposite SNO instance.

Is there any workaround available to the best of your knowledge?

No issues are encountered when creating a BSL using an OBC that is created in the noobaa storage class that is backed with AWS.  Only occurs when backed with LVM storage.

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?

1

Can this issue reproducible?

Yes


Note You need to log in before you can comment on or make changes to this bug.