Fixing LCM action on 500 Server Error

As per the latest APPC Docker Image in ONAP Nexus3, logging into the API Explorer (<APPC_IP>:8282/apidoc/explorer/index.html) then triggering any LCM action in appc-provider-lcm (ex: lcm restart) fails with 500 Server Error. This commit fix this by re-ordering the way that the APP-C karaf features are installed in such a way that the domain-model-lib artifact and other dependencies are found when triggering the LCM actions.

Change-Id: I4177df8a5a034500b889a714599aa71f22395de6
Signed-off-by: Hector Anapan <ha076r@att.com>
Issue: [APPC-169]

diff --git a/installation/appc/src/main/scripts/installFeatures.sh b/installation/appc/src/main/scripts/installFeatures.sh
index 78ad899..8371847 100644 (file)
--- a/installation/appc/src/main/scripts/installFeatures.sh
+++ b/installation/appc/src/main/scripts/installFeatures.sh
@@ -41,7 +41,6 @@ done
 
 APPC_FEATURES=" \
  appc-metric \
- appc-provider \
  appc-command-executor \
  appc-dmaap-adapter \
  appc-event-listener \
@@ -50,6 +49,7 @@ APPC_FEATURES=" \
  appc-rest-adapter \
  appc-lifecycle-management \
  appc-dispatcher \
+ appc-provider \
  appc-dg-util \
  appc-dg-shared \
  appc-asdc-listener \
@@ -76,4 +76,4 @@ do
   else
     echo "No installer found for feature ${feature}"
   fi
-done
+done
\ No newline at end of file