Project

General

Profile

Bug #3572

LDAP not updated for Node when synchronized set to true

Added by Robert Waltz over 9 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
Robert Waltz
Category:
d1_cn_node_registry
Target version:
Start date:
2014-10-01
Due date:
2014-10-01
% Done:

0%

Milestone:
None
Product Version:
Story Points:
Sprint:

Description

possible error in d1_cn_node_registry with regard to change the synch attribute of a node

Ben called updateNodeCapabilities on stage2. Hazelcast Map reflected the change, but the changed indicator was not persisted into ldap.

History

#1 Updated by Robert Waltz over 9 years ago

  • Description updated (diff)

#2 Updated by Robert Waltz about 9 years ago

  • Target version changed from 2013.6-Block.1.3 to 2013.10-Block.2.1
  • Due date changed from 2013-02-13 to 2013-03-16

#3 Updated by Chris Jones about 9 years ago

As another example, Kavitha called CN.updateNodeCapabilities(), setting her Node.Schedule to min="0/3" on cn-stage.test.dataone.org. She received an HTTP 200, but after looking at both LDAP and hzNodes, neither updated with the new Node values.

#4 Updated by Robert Waltz almost 9 years ago

  • Due date changed from 2013-03-16 to 2013-06-22
  • Target version changed from 2013.10-Block.2.1 to 2013.24-Block.3.4

#5 Updated by Robert Waltz almost 9 years ago

  • Milestone changed from CCI-1.1.2 to None
  • Due date deleted (2013-06-22)
  • Target version deleted (2013.24-Block.3.4)
  • Start date deleted (2013-02-13)

Have not been able to reproduce yet.

#6 Updated by Robert Waltz over 7 years ago

  • Start date set to 2014-10-01
  • Target version set to Release Backlog
  • Due date set to 2014-10-01

#7 Updated by Robert Waltz over 6 years ago

  • Related to deleted (Story #3882: Refactor hzNodes out of CN Node Registry)

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)