-
Type: Bug
-
Status: Resolved (View Workflow)
-
Priority: Medium
-
Resolution: Fixed
-
Affects Version/s: 5.0
-
Fix Version/s: None
-
Component/s: Build System
-
Labels:None
-
Story Points:1
-
Sprint:SC Sprint #6
The role of 'Wait for XOS TOSCA engine to be ready after service onboarding' doesnt re-try when the status code is not 200. This seems to have been a bug all along but most of the time didnt fail as its run after xos chameleon is ready and most likely at that point tosca is ready.
TASK [xos-ready : Wait for XOS Chameleon to be ready after service onboarding] *** Thursday 01 February 2018 18:40:13 +0000 (0:00:01.552) 0:00:01.598 ***** FAILED - RETRYING: Wait for XOS Chameleon to be ready after service onboarding (40 retries left). FAILED - RETRYING: Wait for XOS Chameleon to be ready after service onboarding (39 retries left). ok: [localhost] TASK [xos-ready : Wait for XOS TOSCA engine to be ready after service onboarding] *** Thursday 01 February 2018 18:40:54 +0000 (0:00:41.283) 0:00:42.881 ***** fatal: [localhost]: FAILED! => {"changed": false, "connection": "close", "content": "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>503 Service Unavailable</title>\n</head><body>\n<h1>Service Unavailable</h1>\n<p>The server is temporarily unable to service your\nrequest due to maintenance downtime or capacity\nproblems. Please try again later.</p>\n<hr>\n<address>Apache/2.4.7 (Ubuntu) Server at xos-tosca Port 80</address>\n</body></html>\n", "content_length": "373", "content_type": "text/html; charset=iso-8859-1", "date": "Thu, 01 Feb 2018 18:40:54 GMT", "msg": "Status code was not [200]: HTTP Error 503: Service Unavailable", "redirected": false, "server": "Apache/2.4.7 (Ubuntu)", "status": 503, "url": "http://xos-tosca/xos-tosca"} to retry, use: --limit @/opt/cord/build/platform-install/onboard-profile-playbook.retry