BIND 10 #1080: bug in config set <list>[index] where index does not exist

BIND 10 Development do-not-reply at isc.org
Wed Jun 29 14:50:18 UTC 2011


#1080: bug in config set <list>[index] where index does not exist
-------------------------------------+-------------------------------------
            Reporter:  jelte         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  major         |                    Milestone:  New
           Component:  Unclassified  |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 if you have a configuration list, consisting of, say, 2 items (indexed 0
 and 1), and you try to set a value for list[2], it won't error, but
 bindctl will get terribly confused (which is not apparent until you try to
 commit, at which point i think the only way to get out of the inconsistent
 state is to do 'config revert').

 It should immediately error if you try to modify a value in a list item
 that does not exist, and not update internal state.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1080>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list