Bug #4176
The archive method in CN doesn't call back to the authoritative and replica MNs.
Start date:
2014-10-01
Due date:
2014-10-01
% Done:
0%
Milestone:
None
Product Version:
*
Story Points:
Sprint:
Description
All of the CN calls that modify SystemMetadata should be calling back to the authoritative and replica MNs with MN.systemMetadataChanged() to keep them up to date. However, when i tested to use a MN certificate to call the archive method in CN, the system metadata in CN was modified, but the one in the authoritative (original) MN isn't changed. We need also to check all of methods involving to modify SystemMetadata.
History
#1 Updated by Dave Vieglais about 10 years ago
- Start date set to 2014-10-01
- Due date set to 2014-10-01
- Target version set to Maintenance Backlog
#2 Updated by Dave Vieglais about 10 years ago
- Target version deleted (
Maintenance Backlog) - Due date deleted (
2014-10-01) - Start date deleted (
2014-10-01)
#3 Updated by Dave Vieglais about 10 years ago
- Due date set to 2014-10-01
- Start date set to 2014-10-01
- Target version set to Release Backlog