-
Notifications
You must be signed in to change notification settings - Fork 59
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
e2e: Improve logging for channel operations
- Unify state change messages (Create channel, Deleted channel) - Log also channel namespace - Log debug logs (already exists, not found) in DEBUG level Signed-off-by: Nir Soffer <nsoffer@redhat.com> Enhancements to support multiple DRPC in a NS for epic-6681 Signed-off-by: pruthvitd <prd@redhat.com> github-ci: cancel in-progress runs if PR is updated Signed-off-by: Raghavendra Talur <raghavendra.talur@gmail.com> Update Ramen to use the v1beta1 version of the external-snapshotter API Update Ramen imports to use the v1beta1 of the external-snapshotter API Change the way we find snapshots and PVCs and remove the deprecated references of v1alpha1 Signed-off-by: Benamar Mekhissi <bmekhiss@ibm.com> vrg: remove the extra naming in the logger Most of the vrg logs have the name controllers.VolumeReplicationGroup. In this code, we were adding suffix of .vrginstance to it with no use. Signed-off-by: Raghavendra Talur <raghavendra.talur@gmail.com> drenv: added new SC and Pool for RBD This commit adds a new storage class and pool for RBD, which allows the ramen code base to exercise the filtering logic when there are multiple storage classes in the environment. This also prepares the environment for scenarios where more than two workloads use different storage classes. Signed-off-by: rakeshgm <rakeshgm@redhat.com> ceph-fs new sc and fs added The commit adds a new storage classes and pools for Cephfs, which allows the ramen code base to exercise the filtering logic when there are multiple storage classes in the environment. This also prepares the environment for scenarios where more than two workloads use different storage classes. The older Ceph-FS names have been renamed and accordingly the changes have been made to the other test files Signed-off-by: rakeshgm <rakeshgm@redhat.com> Fix CG PVC selection issue due to storageId mismatch on failover Recently, we started using storageId as part of the label to determine whether a PVC belongs to a consistency group. While the initial deployment and synchronization from primary to secondary clusters work correctly, failover or relocation results in a different storageId on the new primary. This mismatch causes issues when setting up the source and destination again. This fix ensures that PVC selection accounts for storageId differences to maintain correct CG membership during failover and relocation. Signed-off-by: Benamar Mekhissi <bmekhiss@ibm.com> drenv: update external-snapshotter addon to v8.2 Update external-snapshotter addon crds & resources from v8.1.0 to v8.2 Signed-off-by: Parikshith <pbyregow@redhat.com> drenv: update rook from 1.15 to 1.16 Signed-off-by: Parikshith <pbyregow@redhat.com> drenv: add patch to enable VolumeGroupSnapshot add patch to enable VolumeGroupSnapshot using feature gate "--feature-gates=CSIVolumeGroupSnapshot=true" Signed-off-by: Parikshith <pbyregow@redhat.com> volrep: Fix archived annotation formatting We converted int64 to int, possibly truncating the value, and then converted it to string and format the string into the result string. Fixed by formatting int64 into the result string. Signed-off-by: Nir Soffer <nsoffer@redhat.com> volrep: Simplify annotation check The check is trivial, ensuring that both pvc and pv have the expected annotation value. The code was too complicated, using complex way to access map value, adding 5 temporary variables, and complex conditions. Simplify to the simplest possible form that anyone will understand quickly. Signed-off-by: Nir Soffer <nsoffer@redhat.com> vrg: don't protect kube resources as secondary during relocation This is not the right place to protect the kube resources as one final sync when we are relocating. It is too late as the user has already been informed to cleanup the resources and some of the resources might have been deleted already. The right time to do it is before the application resource cleanup but we cannot do it right now because of the difference in how volrep and volsync behave. We will fix it in a future release. Signed-off-by: Raghavendra Talur <raghavendra.talur@gmail.com> vrg: improve log message Signed-off-by: Raghavendra Talur <raghavendra.talur@gmail.com> log for progression Signed-off-by: Raghavendra Talur <raghavendra.talur@gmail.com> vrg: differentiate vrg and kube objects upload msg Signed-off-by: Raghavendra Talur <raghavendra.talur@gmail.com> vrg: better logging for conditions Signed-off-by: Raghavendra Talur <raghavendra.talur@gmail.com>
- Loading branch information
Showing
60 changed files
with
932 additions
and
351 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.