[OPENIDM-10923] OpenIDM 6.5 with configuration from 6.0 is not starting with error on Maintenance Bundle Created: 15/May/18  Updated: 16/Nov/18  Resolved: 09/Jul/18

Status: Closed
Project: OpenIDM
Component/s: _Update
Affects Version/s: 6.5.0
Fix Version/s: 6.5.0

Type: Bug Priority: Major
Reporter: Laurent Bristiel [X] (Inactive) Assignee: Jason Lemay
Resolution: Fixed Votes: 0
Labels: CLARK
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

OpenIDM version "6.5.0-SNAPSHOT" (build: 20180514225225, revision: 58543d3) with DJ or MySQL as a repo

Target Version/s:
Verified Version/s:
Story Points: 3
Sprint: OpenIDM Sprint 6.5-4, OpenIDM Sprint 6.5-5


Assumption: “we wish that N+1 still consume N config with no degradation in functionality”

Steps to test this (and reproduce the problem)

  • unzip 6.5.0-SNAPSHOT
  • replace the configuration files (in conf/) by those from the 6.0.0
  • start OpenIDM:
    Executing ./startup.sh...
    Using OPENIDM_HOME:   /Users/laurent/Installs/openidm65
    Using PROJECT_HOME:   /Users/laurent/Installs/openidm65
    Using OPENIDM_OPTS:   -Xmx1024m -Xms1024m
    Using LOGGING_CONFIG: -Djava.util.logging.config.file=/Users/laurent/Installs/openidm65/conf/logging.properties
    -> May 15, 2018 5:21:14 PM org.forgerock.openidm.config.logging.LogServiceTracker logEntry
    SEVERE: Bundle: org.forgerock.openidm.maintenance [243] FrameworkEvent ERROR
    org.apache.felix.log.LogException: org.osgi.framework.BundleException: Unable to resolve org.forgerock.openidm.maintenance [243](R 243.0): missing requirement [org.forgerock.openidm.maintenance [243](R 243.0)] osgi.wiring.package; (&(osgi.wiring.package=org.forgerock.openidm.launcher)(version>=6.5.0)(!(version>=7.0.0))) Unresolved requirements: [[org.forgerock.openidm.maintenance [243](R 243.0)] osgi.wiring.package; (&(osgi.wiring.package=org.forgerock.openidm.launcher)(version>=6.5.0)(!(version>=7.0.0)))]
    	at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4111)
    	at org.apache.felix.framework.Felix.startBundle(Felix.java:2117)
    	at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371)
    	at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
    	at java.lang.Thread.run(Thread.java:745)
    OpenIDM version "6.5.0-SNAPSHOT" (build: 20180514225225, revision: 58543d3) jenkins-OpenIDM-build-master-195
    May 15, 2018 5:21:31 PM org.forgerock.openidm.health.HealthService$4 run
    SEVERE: OpenIDM failure during startup, ACTIVE_NOT_READY: Not all modules started [] [org.forgerock.openidm.maintenance] []

Comment by Alex Bugar [X] (Inactive) [ 06/Jun/18 ]

I also experienced this bug when trying to deploy IDM_6.5-snapshot with Postgres repo in Google Cloud (GKE) using 6.0 config files. Kubernetes deployment is not possible without a fix here..  Thx 

Comment by Jason Lemay [ 18/Jun/18 ]

This error occurs because of this line in the config.properties.


For 6.5 the version of the org.forgerock.openidm.launcher package needs to be 6.5.0 and not 6.0.0.

One potential solution is to remove the version specification for that package since we only ever deliver one version of that package for 6.5+. This solution will still require upgrade documentation to remove the version specification in the 6.0 config.properties file.

Another solution is to figure out why org.forgerock.openidm.launcher is specified in that configuration property and remove it if it is not needed, or find out if there is another way of providing that package.

Comment by Jason Lemay [ 09/Jul/18 ]

This issue has been resolved on master. The fix was to not specify the version of the launcher package in the config.properties. We should not be able to start IDM 6.5 with IDM 6.0 config.

Comment by Laurent Bristiel [X] (Inactive) [ 16/Nov/18 ]

Checked OK in OpenIDM version "6.5.0-SNAPSHOT" (build: 20181114225033, revision: b90b2ee). The update process was since retested OK by several people and will be re-tested before final release of 6.5

Generated at Tue Nov 24 00:53:44 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.