Bug 509401 - dnaNextValue is not updated when dnaNextvalue is set to -1
Summary: dnaNextValue is not updated when dnaNextvalue is set to -1
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: 389
Classification: Retired
Component: Server - DNA Plug-in
Version: 1.2.1
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Nathan Kinder
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks: 434914 389_1.2.1
TreeView+ depends on / blocked
 
Reported: 2009-07-02 15:54 UTC by Nathan Kinder
Modified: 2015-12-07 16:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-07 16:58:00 UTC


Attachments (Terms of Use)
Patch (1.47 KB, patch)
2009-07-02 16:19 UTC, Nathan Kinder
no flags Details | Diff

Description Nathan Kinder 2009-07-02 15:54:36 UTC
When "dnaMaxValue" is set to "-1" or omitted from a range configuration entry (which defautls to "-1" internally), the "dnaNextValue" attribute is not updated in the range configuration entry when a value is allocated from that range.

Whenever a value is allocated from the range, the "dnaNextValue" attribute should be updated accordingly.

Comment 1 Nathan Kinder 2009-07-02 16:19:47 UTC
Created attachment 350310 [details]
Patch

We were only updating the configuration entry if the new nextvalue was >=
the maxval plus the interval (1).  We need to check if the maxval is -1
specifically, and update the config entry if so.

Comment 2 Nathan Kinder 2009-07-02 17:01:59 UTC
Pushed to master.  Thanks to Rich for his review!

Comment 3 Sudhir D 2009-07-02 17:31:37 UTC
Changed QA contact to Sudhir

Comment 4 Sudhir D 2009-07-08 06:51:50 UTC
This is verified on RHDS 9.0 and fix is working as expected.


Note You need to log in before you can comment on or make changes to this bug.