Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug 2252880: volumes are lost on the secondary managed cluster after hub recovery #161

Closed
wants to merge 3 commits into from

Conversation

rakeshgm
Copy link
Member

@rakeshgm rakeshgm commented Dec 8, 2023

No description provided.

Upon hub recovery, it is essential to regenerate the VRG ManifestWorks. For CephFS workloads,
two VRG ManifestWorks are necessary—one for the primary cluster and another for the secondary
cluster. However, Ramen failed to regenerate the secondary VRG ManifestWork due to a bug. The
bug originated from a condition that determined whether to regenerate the ManifestWork based
solely on the number of VRGs found on the managed cluster. Consequently, if the count met the
required number, the regeneration was bypassed without considering the actual count of
ManifestWorks. This oversight led to ACM evicting the VRG from the secondary cluster after
the default one-hour eviction time.

Signed-off-by: Benamar Mekhissi <[email protected]>
(cherry picked from commit d9b5ffa)
Signed-off-by: Benamar Mekhissi <[email protected]>
(cherry picked from commit 9dd1c15)
Signed-off-by: Benamar Mekhissi <[email protected]>
(cherry picked from commit ca7af2d)
Copy link

openshift-ci bot commented Dec 8, 2023

@rakeshgm: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

Bz2252880

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Copy link

openshift-ci bot commented Dec 8, 2023

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rakeshgm

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rakeshgm rakeshgm changed the title Bz2252880 Bug 2252880: volumes are lost on the secondary managed cluster after hub recovery Dec 8, 2023
Copy link

openshift-ci bot commented Dec 8, 2023

@rakeshgm: This pull request references Bugzilla bug 2252880, which is invalid:

  • expected the bug to target the "ODF 4.14.1" release, but it targets "ODF 4.14.2" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 2252880: volumes are lost on the secondary managed cluster after hub recovery

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ShyamsundarR
Copy link

Closing as this is merged via #160

Copy link

openshift-ci bot commented Dec 8, 2023

@rakeshgm: An error was encountered removing this pull request from the external tracker bugs for bug 2252880 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details.

Full error message. response code 400 not 200

Please contact an administrator to resolve this issue, then request a bug refresh with /bugzilla refresh.

In response to this:

Bug 2252880: volumes are lost on the secondary managed cluster after hub recovery

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants