[FELIX-5248] SCR does not reactivate a failed component after a configuration update

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: scr-2.0.4
• Fix Version/s: scr-2.0.6
• Component/s: Declarative Services (SCR)
• Assignee: David Jencks
• Reporter: Timothy James Ward
• Created: 03/May/16 16:22
• Updated: 16/Mar/17 20:06
• Resolved: 16/Mar/17 20:06

Description

A configurable SCR component may fail to activate by throwing an exception if the factory configuration contains bad values. If the factory configuration for that component is then updated SCR should attempt to recreate and activate the component. Instead the component sits in the "satisfied" state forever, and updates to the factory configuration are ignored.

This makes it impossible to "fix" a mistaken configuration without deleting and recreating it.