BIND 10 #1491: Boss/components config option got set to empty

[BIND 10 Development]

#1491: Boss/components config option got set to empty
-------------------------------------+-------------------------------------
            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
-------------------------------------+-------------------------------------
 I was playing around a bit with the 'kind' option in Boss/components, and
 changing it results in an error (as this is currently not supported; see
 #1413), removing it and readding it also leads to the same error (without
 intermediate commit, that is), and after that, the components set had been
 set to empty. This meant that no non-core processes were running anymore,
 and, most importantly cmdctl had stopped (so only manual fixing of the
 config file worked).

 This looks like an error in cfgmgr (where it doesn't recover from update
 checks correctly).

 The symptoms for this specific case will disappear if #1413 gets done, and
 for when a thing like this happens (and there may be more cases where we
 get 'bad' config file, even cases out of our control), we need to do
 #1443, and/or allow offline-configuration (for instance so that bindctl
 can work directly on the b10-config.db file, if it can't connect to
 cmdctl)

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