-
Notifications
You must be signed in to change notification settings - Fork 4
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: Exclude VolSync secret Policy from hub backup & regenerate ManifestWork on hub restore #160
Bug 2252880: Exclude VolSync secret Policy from hub backup & regenerate ManifestWork on hub restore #160
Conversation
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)
@BenamarMk: This pull request references Bugzilla bug 2252933, which is invalid:
Comment In response to this:
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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: BenamarMk 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 |
@BenamarMk: An error was encountered removing this pull request from the external tracker bugs for bug 2252933 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 In response to this:
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. |
@BenamarMk: This pull request references Bugzilla bug 2252880, which is invalid:
Comment In response to this:
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. |
@BenamarMk: This pull request references Bugzilla bug 2252880, which is invalid:
Comment In response to this:
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. |
a1a89f6
into
red-hat-storage:release-4.14
@BenamarMk: All pull requests linked via external trackers have merged: Bugzilla bug 2252880 has been moved to the MODIFIED state. In response to this:
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. |
No description provided.