[CONTROLLER-935] Clustering : Installing Distribution downloaded from opendaylight is not working. Created: 14/Oct/14 Updated: 29/Oct/14 Resolved: 29/Oct/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Narayana Rao Kankipati | Assignee: | Mark Mozolewski |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 2189 |
| Description |
|
description: distribution used to install : distribution-karaf-0.2.0-Helium.zip ISSUE: under : /opendaylight/integration/test/tools/cluster-deployer/templates/openflow file:org.apache.karaf.features.cfg.template 0.2.0-SNAPSHOT is needs to be changed to 0.2.0-Helium <<<<<<< <snip> from file: org.apache.karaf.features.cfg.template |
| Comments |
| Comment by Narayana Rao Kankipati [ 14/Oct/14 ] |
|
steps to reproduce: 1) download the deploy.py test script from /opendaylight/integration/test/tools/cluster-deployer in your local host machine 2) don't modify any files under templates/openflow folder 3) download the distribution-karaf-0.2.0-Helium.zip and save it under any folder in your local machine from where you are running the deploy.py 3) run the script.. deploy.py script python deploy.py --distribution=/distribution-karaf-0.2.0-Helium.zip --hosts=xx.xx.xx.xa,xx.xx.xx.xb,xx.xx.xx.xc --rootdir=/root --user=<userid> --password=<password> |
| Comment by Mark Mozolewski [ 24/Oct/14 ] |
|
Fix submitted: https://git.opendaylight.org/gerrit/12210 Tested with deploy.py script and 3 local VMs per the bug filing instructions. Note: I also fixed an issue with loading Jolokia 1.1.5v in Karaf that I noticed in the logs during testing. |
| Comment by Mark Mozolewski [ 29/Oct/14 ] |
|
Merged: https://git.opendaylight.org/gerrit/#/c/12303/ Note that version of ODL distribution is now pulled from the file name passed in to deploy.py with the "distribution" argument so the deployment template should not have this issue in the future with different distributions. |