Bug 2132359 - Remove workaround to create and tickle dummy image for volume promotion
Summary: Remove workaround to create and tickle dummy image for volume promotion
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: csi-driver
Version: 4.12
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.12.0
Assignee: Madhu Rajanna
QA Contact: Pratik Surve
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-05 12:01 UTC by Shyamsundar
Modified: 2023-08-09 16:37 UTC (History)
7 users (show)

Fixed In Version: 4.12.0-74
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-08 14:06:28 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-csi pull 3413 0 None open rbd: remove dummy image workaround 2022-10-05 15:19:03 UTC

Description Shyamsundar 2022-10-05 12:01:29 UTC
Description of problem (please be detailed as possible and provide log
snippests):

To address the problem that snapshot schedules are triggered for volumes that are promoted, a dummy image was disabled/enabled for replication. This was done as a workaround, because the promote operation was not triggering the schedules for the image being promoted.

The bugs related to the same have been fixed in Ceph-RBD mirroring functionality and hence the workaround can be removed from the code base.

Code added with PR starting here: https://github.com/ceph/ceph-csi/pull/2656
Parent BZ that triggered the workaround: https://bugzilla.redhat.com/show_bug.cgi?id=2019161

Version of all relevant components (if applicable):

Needs removal only from 4.12 onward

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

No

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

NA

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

2
(as we need to ensure the older issue no longer exists in the later ceph versions to ensure the workaround can be safely removed)

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
NA

Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:


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