Bug #3699
CN.updateReplicaMetadata preventing valid update
100%
Description
Discovered while testing replica auditing. The business logic in CNodeService.updateReplicationMetadata prevents an update to the verification date when the replica status is 'completed'. It may be that the status change business logic need only be invoked when the status is changing. Prevents auditing from updating valid replicas with a new verification date.
Redmine3699.patch 
(1.24 KB)
History
#1 Updated by Skye Roseboom about 11 years ago
- Status changed from New to In Progress
- Assignee changed from Chris Jones to Skye Roseboom
Creating a patch update for this issue.
#2 Updated by Skye Roseboom about 11 years ago
- File Redmine3699.patch added
patch file attached.
Only throws InvalidRequest regarding invalid status change of a 'completed' replica if the replica status is changing.
#3 Updated by Skye Roseboom about 11 years ago
- Assignee changed from Skye Roseboom to Matthew Jones
Hi Matt - could you sanity check this patch and commit to metacat?
It is a minor one line change - such that the replica status change validation need only be performed when the status is changing. (Comparing incoming replica's status to the existing replica status)
thanks!
#4 Updated by Ben Leinfelder about 11 years ago
- Assignee changed from Matthew Jones to Ben Leinfelder
I will incorporate this so it is included in v2.0.6
#5 Updated by Ben Leinfelder about 11 years ago
- Status changed from In Progress to Closed
