-
Notifications
You must be signed in to change notification settings - Fork 38
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
replication: update LastSyncTime if its not nill #260
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works to not update last known lastSyncTime in cases where the call does not return a value, or hold it at epoch till it does.
NOTE: As I have not cross-checked other areas of code not approving as such.
@nixpanic PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Marking this -1 until the discussion in csi-addons/spec#47 is resolved.
Pull request has been modified.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
@Mergifyio rebase |
LastSyncTime can be optional and nil also, there is no strict check for it and if we dont have this check the default UNIX time will get added to the CR which doesnt make sense. If the time is not present keeping the last known LastSyncTime itself. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
csi-addons/spec#47 has the defined errors for the GetVolumeReplicationInfo RPC call. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
Added known error for GetVolumeReplicationInfo RPC call as per the predefined error messages in the csiaddons spec. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
✅ Branch has been successfully rebased |
c31bad2
to
8df5465
Compare
LastSyncTime can be optional and nil also, there is no strict check for it, and if we dont have this check the default UNIX time will get added to the CR, which doesn't make sense. If the time is not present keep the last known LastSyncTime itself.
Depends-On: csi-addons/spec#47