Bug 509401

Summary: dnaNextValue is not updated when dnaNextvalue is set to -1
Product: [Retired] 389 Reporter: Nathan Kinder <nkinder>
Component: Server - DNA Plug-inAssignee: Nathan Kinder <nkinder>
Status: CLOSED CURRENTRELEASE QA Contact: Viktor Ashirov <vashirov>
Severity: medium Docs Contact:
Priority: low    
Version: 1.2.1CC: benl, jgalipea, rmeggins, sdharane
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-07 16:58:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 434914, 517385    
Attachments:
Description Flags
Patch none

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.