[GitHub] incubator-metron issue #563: METRON-840: All "ambari_*" hosts need to have a...

[nickwallen <gi...@git.apache.org>]

Github user nickwallen commented on the issue:

    https://github.com/apache/incubator-metron/pull/563
  
    When spinning this up on EC2, I ran into this problem.  Ever seen this before?  Maybe unrelated to your PR.
    
    ```
    TASK [ambari_config : Deploy cluster with Ambari; http://ec2-54-236-37-116.compute-1.amazonaws.com:8080] ***
    fatal: [ec2-54-236-37-116.compute-1.amazonaws.com]: FAILED! => {"changed": false, "failed": true, 
    "msg": "Ambari client exception occurred: Could not create blueprint: request code 400,                     
    request message {\n  \"status\" : 400,\n  \"message\" : \"Blueprint configuration validation failed: 
    Missing required properties.  Specify a value for these properties in the blueprint configuration. 
    {metron={metron-env=[metron_jdbc_platform, metron_jdbc_driver, metron_jdbc_username, metron_jdbc_url]}}\"\n}"}
    ```
    
    Then when re-running, I get a slightly different error.
    ```
    TASK [ambari_master : Setup ambari server] *************************************
    fatal: [ec2-54-236-37-116.compute-1.amazonaws.com]: FAILED! => {"changed": false, "cmd": 
    "ambari-server setup -s && touch /etc/ambari-server/configured", "failed": true, 
    "failed_when_result": true, "rc": 0, "stderr": false, 
    "stdout": "skipped, since /etc/ambari-server/configured exists", 
    "stdout_lines": ["skipped, since /etc/ambari-server/configured exists"]}
    ```


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---