Hemant Kumar
Hemant Kumar
/payload-job periodic-ci-openshift-cluster-storage-operator-release-4.18-e2e-aws-group-snapshot-tp 3
/payload-job periodic-ci-openshift-cluster-storage-operator-release-4.18-e2e-aws-group-snapshot-tp
/payload-job periodic-ci-openshift-cluster-storage-operator-release-4.18-e2e-aws-group-snapshot-tp
Also can we add unit test for this scenario? 1. Create a volumegroupsnapshotclass. 2. Create one or more PVCs that use volumes. 3. Take snapshot of those PVCs via `volumegroupsnapshot`...
@ShyamsundarR thank you for tagging me. So unless ceph itself can provide strong guarantees about preventing volume attach to multiple nodes for block volumes, we should not disable external-attacher. Evidence...
@leonardoce can you update this PR to resolve the conflicts?
We should compile this branch rebased with master and then run e2e tests in a loop for sometime. I have often done this for testing pre-release code which needs more...
I noticed that following field in `volumeGroupSnapshot.Status` is user editable after setting it: ``` BoundVolumeGroupSnapshotContentName *string `json:"boundVolumeGroupSnapshotContentName,omitempty" protobuf:"bytes,1,opt,name=boundVolumeGroupSnapshotContentName"` ``` Should this be immutable after creation?
>This field is in the Status. Are we supposed to make fields in Status immutable? We have not done that for VolumeSnapshot APIs. It would have been nice to have....