Hi Adam, Got the point. I had suspected the same. I have repo_url http://repo.cw-ngv.com/stable in heat's env file.
Is it possible to use same release on which ONAP's heat templates are based, may be by changing this repo URL? I will have a look at current heat template on Clearwater GitHub but I think those won't be ONAP compatible. From: Clearwater [mailto:[email protected]] On Behalf Of Adam Lindley Sent: Tuesday, December 12, 2017 10:50 PM To: [email protected] Subject: Re: [Project Clearwater] 502 Bad Gateway and other errors while running live tests Do you know which release you based the templates on? We should be able to take a look over our release notes between then and now, which should give a reasonable view of the changes, and then we can go from there. Equally, the commit history (https://github.com/Metaswitch/clearwater-heat/commits/stable) gives a fairly clear overview of what and why, with the pull requests adding a bit more detail. Though as we're likely to hit similar problems in future as we continue to develop Project Clearwater and our heat templates. Are the ONAP changes something we could be pulling in to the main code base? I'd be interested to know the extent of the work needed to keep them running From: Clearwater [mailto:[email protected]] On Behalf Of Mike Evans Sent: 12 December 2017 17:00 To: [email protected]<mailto:[email protected]> Subject: Re: [Project Clearwater] 502 Bad Gateway and other errors while running live tests Adam I put the ONAP templates together, so I'm happy to update them if they won't work with the latest Project Clearwater code. Is there anywhere I can look for an explanation of the changes? Mike From: Clearwater [mailto:[email protected]] On Behalf Of Adam Lindley Sent: 12 December 2017 16:41 To: [email protected]<mailto:[email protected]> Subject: Re: [Project Clearwater] 502 Bad Gateway and other errors while running live tests Hi Kedar, I've just had a look around for the templates on the ONAP wiki; I wasn't aware they had their own copies of them. I found https://wiki.onap.org/display/DW/Clearwater+vIMS+Onboarding+and+Instantiation . Is this what you've been working from? When deploying with the templates, have you been specifying a "repo_url" option in the arguments? The Clearwater HEAT templates included steps to install the Clearwater packages from our public stable repo by default, but the templates on the ONAP wiki are now somewhat out of date. If you haven't specified a repo containing packages from the same point in time the templates were effectively forked, you're going to be hitting conflicts between the code version, and the orchestration steps. I am not sure what differences there need to be for templates to run on ONAP, but I can point you towards our current set of heat templates: https://github.com/Metaswitch/clearwater-heat/tree/stable . I would suggest you try redeploying with these templates, as a fair number of things have changed in the code since the templates on the wiki were valid. If you hit any issues, do let us know. Cheers, Adam From: Clearwater [mailto:[email protected]] On Behalf Of Kedar Ambekar Sent: 12 December 2017 13:46 To: [email protected]<mailto:[email protected]> Subject: [Project Clearwater] 502 Bad Gateway and other errors while running live tests Hi, I have installed Clearwater with heat templates (available on ONAP wiki) directly on openstack. Appreciate help on below issues. 1. When I run Clearwater live tests, all tests fail with below error. RuntimeError thrown: - Account creation failed with HTTP code 502, body {"status": 502, "message": "Bad Gateway", "reason": "Upstream request failed", "detail": {"Upstream error": "599", "Upstream URL": "None"}, "error": true} 1. ps for bono process shows this. [bono]ubuntu@0:/etc/clearwater$ ps -ef |grep bono bono 6897 1 0 05:06 ? 00:00:11 /usr/share/clearwater/bin/bono --domain= --localhost=10.0.0.28,0.bono.me.cw-ngv.com --al ias=10.0.0.28,0.bono.me.cw-ngv.com, --pcscf=5060,5058 --webrtc-port=5062 --routing-proxy=icscf.,5052,50,600 --sas=0.0.0.0,[email protected] --dns-server=127.0.0.1 --worker-threads=2 --analytics=/var/log/bono --log-file=/var/log/bono --log-level=2 --daemon --pidfile=/var/run/bono/bono.pid 1. In bono, I saw these logs. UTC Error sip_connection_pool.cpp:190: Failed to resolve icscf. to an IP address - Not found (PJ_ENOTFOUND) UTC Warning dnscachedresolver.cpp:828: Failed to retrieve record for icscf.: Domain name not found 1. To debug above issues, I ended up making these changes in /etc/init.d/bono and restarted bono service. DAEMON_ARGS="--domain=me.cw-ngv.com (instead of -domain=$home_domain) upstream_hostname=icscf.sprout.me.cw-ngv.com (instead of upstream_hostname=icscf.$sprout_hostname) 1. But now, I get below error in bono. Port 5052 is not in listen mode on sprout. UTC Warning pjsip: tcpc0x7f90cc07 TCP connect() error: Connection refused [code=120111] UTC Warning pjsip: tcpc0x7f90cc07 Unable to connect to <sprout ip>:5052 ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
