BalintSzigeti
commented
5 years ago The issue was caused by myself. I deleted few services from group_vars/all which I don't use and the blueprint role could not handle it. Once I rolled back the deletion, the role could be applied.
I followed the instructions and I got topology validation error when blueprint role should be applied.
fatal: [ec2-****.us-west-2.compute.amazonaws.com]: FAILED! => {"cache_control": "no-store", "changed": false, "connection": "close", "content": "{\n \"status\" : 400,\n \"message\" : \"Cluster Topology validation failed. Invalid service component count: [HST_SERVER(actual=0, required=1), OOZIE_SERVER(actual=0, required=1+)]. To disable topology validation and create the blueprint, add the following to the end of the url: '?validate_topology=false'\"\n}", "content_type": "text/plain;charset=utf-8", "date": "Sat, 01 Dec 2018 11:15:09 GMT", "expires": "Thu, 01 Jan 1970 00:00:00 GMT", "json": {"message": "Cluster Topology validation failed. Invalid service component count: [HST_SERVER(actual=0, required=1), OOZIE_SERVER(actual=0, required=1+)]. To disable topology validation and create the blueprint, add the following to the end of the url: '?validate_topology=false'", "status": 400}, "msg": "Status code was 400 and not [200, 201, 202, 409]: HTTP Error 400: Bad Request", "pragma": "no-cache", "redirected": false, "set_cookie": "AMBARISESSIONID=node01cquhcwxberao1cexdpriqvgv115.node0;Path=/;HttpOnly", "status": 400, "url": "http://*******.us-west-2.compute.internal:8080/api/v1/blueprints/mytestcluster_blueprint", "user": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER", "x_content_type_options": "nosniff, nosniff", "x_frame_options": "DENY", "x_xss_protection": "1; mode=block"}