[METRON-935] EC2 Deployment Failure - Could Not Create Blueprint

• Type: Bug
• Status: Done
• Priority: Blocker
• Resolution: Done
• Affects Version/s: 0.3.1
• Fix Version/s: 0.4.0
• Assignee: Ryan Merriman
• Reporter: Nick Allen
• Created: 06/May/17 18:05
• Updated: 27/Jun/17 00:08
• Resolved: 12/May/17 13:24

Description

When deploying Metron with EC2, I ran into this problem.

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}"}

Issue Links

• blocks: METRON-905 Fix square-bracket behavior and default network interface bindings for ES
• blocks: METRON-840 All "ambari_*" hosts need to have a /localrepo folder
• links to: GitHub Pull Request #568