-
Bug
-
Resolution: Done
-
Medium
-
Beijing Release
-
None
Steps To Reproduce :
====================
#What steps to follow to recreate the bug
1. ssh to setup - 10.147.97.243
2. Create folder /tmp/$folder
3. wget
+ http://10.147.249.4/asdc_builds/asdc_builds/1806.0.0.141/migration/openecomp-zusammen-tools-lib.zip
3. unzip openecomp-zusammen-tools-lib.zip
4. chmod +x ./zusammenMainTool.sh
5. ./zusammenMainTool.sh -c RESET_OLD_VERSION -v 1802
Expected Behavior
=====================
#What was supposed to happen after completing the above steps
shell script should run successfully and healing flag should be set to True in dox.healing table in cassandra
Actual Behavior
=====================
#What actually happens after completing the above steps
Healing tool failed to run with below logs :
0
Configuration file location: /opt/app/jetty/base/be/config/catalog-be/configuration.yaml
Error: Could not find or load main class lib.build-helper-1806.0.0.jar
Affected Area :
=====================
#Which area of the product is affected: FE, BE, DB, … ?
DB
Specific Error Message :
=====================
#What error is visible to the end user? (FE, BE)
0
Configuration file location: /opt/app/jetty/base/be/config/catalog-be/configuration.yaml
Error: Could not find or load main class lib.build-helper-1806.0.0.jar
Logs :
=====================
#Snippet of the log showing, e.g. Exception stack trace
Environment Setup
=====================
- What does the SUT include?
- Software versions \ builds,
- Physical \ Virtual resources,
- Setup IP \ Cluster-Name
10.147.97.243
Build number :
=====================
=====================
Amdocs build :
#141