Story #7419
hasReservation should not check if an Identifier is already registered
Status:
Closed
Priority:
Normal
Assignee:
Category:
d1_identity_manager
Target version:
Start date:
2015-10-08
Due date:
% Done:
100%
Story Points:
Sprint:
Description
The current implementation of hasReservation returns an IdentifierNotUnique exception if the identifier being checked is already assigned to an object on the CN. This behavior is thought to be confusing, so it was decided to remove this feature from the implementation. reserveIdentifier will still keep this functionality (is is intuitive to throw an exception if the reservation cannot be made because the identifier is already in use).
hasReservation is used extensively by d1_synchronization, but thought not to be used much elsewhere, so we intend to change both the v2 and v1 implementations.
Subtasks
Related issues
Associated revisions
History
#1 Updated by Ben Leinfelder about 9 years ago
- Related to Bug #7386: the ReserveIdentifierService allows SIDs already in use to be reserved. added
#2 Updated by Rob Nahf about 9 years ago
- Related to Bug #7264: CNCore.hasReservation null Subject parameter added
#3 Updated by Robert Waltz about 9 years ago
- Related to Bug #7431: NodelistUtil.getNode returns null for valid nodelist entry added
#4 Updated by Ben Leinfelder almost 9 years ago
- Assignee changed from Ben Leinfelder to Dave Vieglais
#5 Updated by Rob Nahf almost 9 years ago
- % Done changed from 0 to 30
- Status changed from New to In Progress
#6 Updated by Dave Vieglais over 8 years ago
- Status changed from In Progress to Closed
- % Done changed from 30 to 100
