Opened 9 years ago

Closed 8 years ago

Last modified 8 years ago

#1080 closed defect (fixed)

bug in config set <list>[index] where index does not exist

Reported by: jelte Owned by:
Priority: medium Milestone: Sprint-20110830
Component: Unclassified Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

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.

Subtickets

Change History (4)

comment:1 Changed 9 years ago by shane

  • Milestone changed from New Tasks to Next-Sprint-Proposed

comment:2 Changed 9 years ago by stephen

  • Estimated Difficulty changed from 0.0 to 3

comment:3 Changed 8 years ago by jelte

  • Resolution set to fixed
  • Status changed from new to closed

This has been fixed as part of #926, closing.

comment:4 Changed 8 years ago by stephen

  • Estimated Difficulty changed from 3.0 to 0
  • Milestone changed from Next-Sprint-Proposed to Sprint-20110830

Moved to Sprint-20110830 (where it was completed). Estimate set to 0 as no work was done on this task, it being completed as part of #926.

Note: See TracTickets for help on using tickets.