-
Couldn't load subscription status.
- Fork 580
rbd: return replication status and status message in case of error #5500
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
Conversation
5552a0a to
81a26a3
Compare
1472cc4 to
e34dc39
Compare
|
Looks reasonable to me, do you want to adjust the commit message and the description of this PR to clarify things a little more? Specially in the PR description, an example of what was missing, and how it will look like afterwards would be very helpful. |
Sure, updated the description to add some more context. |
|
@Mergifyio rebase |
we should return the status and status message even if we fail to fetch the local status of the volume/group so that the error/state can be propagated to the VR/VGR in csi-addons. Signed-off-by: Nikhil-Ladha <[email protected]>
✅ Branch has been successfully rebased |
e34dc39 to
4998836
Compare
|
@Mergifyio queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 7458910 |
|
/test ci/centos/k8s-e2e-external-storage/1.32 |
|
/test ci/centos/k8s-e2e-external-storage/1.33 |
|
/test ci/centos/mini-e2e-helm/k8s-1.32 |
|
/test ci/centos/k8s-e2e-external-storage/1.31 |
|
/test ci/centos/mini-e2e-helm/k8s-1.33 |
|
/test ci/centos/mini-e2e/k8s-1.32 |
|
/test ci/centos/mini-e2e-helm/k8s-1.31 |
|
/test ci/centos/mini-e2e/k8s-1.33 |
|
/test ci/centos/mini-e2e/k8s-1.31 |
|
/test ci/centos/upgrade-tests-cephfs |
|
/test ci/centos/upgrade-tests-rbd |
Describe what this PR does
We should return the status and status message even if we fail to fetch the local status of the volume/group so that the error/state can be propagated to the VR/VGR in csi-addons.
For ex, if the local mirror status is
down+unknownwhen rbd is not able to fetch the mirror status, we should report the same on the VR/VGR i.e, thestatebeingunknownand the message beingstatus not found.Also, it seems more logical to return a
FailedPreConditionerror code ifsync info not founderror is hit.