[SLING-5888] Health Check for detecting not-installed configurations/bundles from the OSGi installer

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Installer Health Checks 1.0.0
• Component/s: Health Check, Installer
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 22/Jul/16 08:30
• Updated: 15/May/20 08:59
• Resolved: 17/Aug/16 11:19

Description

We faced an issue in the past that configurations (or bundles) being deployed in the repository are not effective (i.e. not installed in Apache Felix).

The reason for that is that the OSGi configuration was either manually modified in the Web Console (and therefore takes precedence over the version of the configuration being deployed in the repository) or in case of bundles, that the same bundle has already been deployed in that or a newer version (manually or through some other path in the repository/filesystem).

Both states may lead to issues at run time, so it would be good to have an automated check for it.

Issue Links

• is related to: SLING-7736 OSGi Installer: Update OSGi installer's resource state in case of configuration/bundle updates outside of the OSGi Installer when JCR Installer Writeback is disabled
• is related to: SLING-7735 OSGi installer configuration is marked as "IGNORED" in case the ConfigurationAdmin contains the correct configuration state already
• is related to: SLING-7479 Add Sling Installer Health Check bundle to Sling Starter
• is related to: SLING-7569 Also warn in case if only one of the supplied bundles/configurations within a group below the configured paths are valid