Plugins will crash if user changes configs values not include port number

[Yevgen R.]

Plugins use configs to get port number for forming cluster info urls (hadoop, oozie) without any validation.

[Matthew Farrellee (mattf)]

If a user changes hadoop configurations that contain a port by default (e.g. dfs.http.address) to not contain a port, the cluster startup will fail without a meaningful error to the user.

[Andrew Lazarev (alazarev)]

The bug was covered by https://review.openstack.org/#/c/66322

Cluster still ends in Error state if user doesn't include port where Hadoop expects it. But this is more general problem - hadoop configs validation. So, if user doesn't include port in dfs.http.address (like Matt mentioned) cluster fails to start because namenode service didn't start. The same effect will be if user enters wrong value as dfs.http.address but with port included.

So, Sahara issue is fixed. Hadoop config validation is much more generic problem than just port validation.

Closing as resolved.