Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/1060
Turns out this is (in theory) done by the service advisor at
https://github.com/apache/metron/blob/ff1f9cf52b31ae866eb3de1cf8993af97af1790f/metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/service_advisor.py#L137
which doesn't look to have been significantly tested (doesn't for example work
on a real cluster, and only works with overrides to blueprint templates to
force application of settings (since the required field insists you enter a
custom value). That therefore doesn't fire in default Ambari blueprint
installs.
You won't see that on full dev, or a platform that explicitly sets
storm_rest_addr in blueprints to a correct value, but on something like a
cloudbreak install (where you can't change the ambari configStrategy) it is
impossible to get the service advisor to run. Since the fields in question are
marked required, the service advisor cannot override them, and the blueprint
cannot be submitted without setting them, so you're in a catch 22 if you do not
know the host names upfront prior to install (the cloud install case).
In any case, this is probably not a good Apache fix, since from the Apache
point of view this already 'works as designed'. Maybe I should file a separate
ticket on the removing the required attribute from the settings which are not
actually required, or it should be handled by rewriting the automation engine
elsewhere, which would allow the service advisor to set them.
---
