[
https://issues.apache.org/jira/browse/METRON-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101752#comment-16101752
]
Oliver Fletcher commented on METRON-1066:
-----------------------------------------
Looking at the error message it seems like the blueprint expects:
Blueprint configuration validation failed: Missing required properties. Specify
a value for these properties in the blueprint configuration.
{noformat}{metron={metron-rest-env=[metron_jdbc_driver, metron_jdbc_username,
metron_jdbc_url]}}{noformat}
I can see the following configurations in:
metron/metron-deployment/roles/ambari_config/vars/small_cluster.yml
{noformat}
required_configurations:
- metron-env:
storm_rest_addr: "http://{{ groups.ambari_slave[1] }}:8744"
es_hosts: "{{ groups.web[0] }},{{ groups.search | join(',') }}"
zeppelin_server_url: "{{ groups.zeppelin[0] }}"
metron_jdbc_driver: "org.h2.Driver"
metron_jdbc_url: "jdbc:h2:file:~/metrondb"
metron_jdbc_username: "root"
metron_jdbc_password: "root"
metron_jdbc_platform: "h2"
- kibana-env:
kibana_pid_dir: /var/run/kibana
kibana_es_url: http://{{ groups.web[0] }}:9200
kibana_log_dir: /var/log/kibana
kibana_server_port: 5000
kibana_default_application: "dashboard/Metron-Dashboard"
{noformat}
Are these variables not being picked up by the logic that generates the
blueprint?
> Metron deployment (AWS) ansible failure deploying blueprint
> -----------------------------------------------------------
>
> Key: METRON-1066
> URL: https://issues.apache.org/jira/browse/METRON-1066
> Project: Metron
> Issue Type: Bug
> Affects Versions: 0.4.1
> Environment: MacOS Sierra 10.12.5
> Reporter: Oliver Fletcher
> Priority: Minor
>
> Hi,
> I've been experiencing successive failure using the ansible AWS deployment
> script:
> {noformat}
> 2017-07-26 15:07:25,471 p=8370 u=labuser | TASK [ambari_config : Deploy
> cluster with Ambari;
> http://ec2-54-171-72-114.eu-west-1.compute.amazonaws.com:8080] ***
> 2017-07-26 15:07:26,475 p=8370 u=labuser | fatal:
> [ec2-54-171-72-114.eu-west-1.compute.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-rest-env=[metron_jdbc_driver,
> metron_jdbc_username, metron_jdbc_url]}}\"\n}"}
> 2017-07-26 15:07:26,477 p=8370 u=labuser | to retry, use: --limit
> @/Users/labuser/projects/metron/metron-deployment/amazon-ec2/playbook.retry
> {noformat}
> I believe this has been introduced during the last few updates - as I've
> previously (successfully) deployed metron using the ansible playbook.
> It seems that the blueprint is now being rejected by Ambari (since 4.0.1?).
> Are there some steps I could follow to further narrow down exactly what is
> causing this issue? I've left the partially deployed infrastructure up so I
> can help troubleshoot this issue.
> Cheers,
> Ollie
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
