[jira] [Updated] (AMBARI-13967) Ranger partial install causes Starts All to do nothing (no pop-up), and Hosts Stop All Components breaks

["Hari Sekhon (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-13967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hari Sekhon updated AMBARI-13967:
---------------------------------
    Summary: Ranger partial install causes Starts All to do nothing (no pop-up), and Hosts Stop All Components breaks  (was: Ranger partial install causes Host All Starts to fail, prevents Cluster Services Start to not trigger at all (no pop-up))

> Ranger partial install causes Starts All to do nothing (no pop-up), and Hosts Stop All Components breaks
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13967
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13967
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>         Environment: HDP 2.2
>            Reporter: Hari Sekhon
>            Priority: Critical
>
> One of my clusters has Ranger service installed (but not yet configured) which causes Ambari to be unable to manage it's services.
> Doing Actions -> "Start All" from Dashboard doesn't absolutely nothing (no pop-up appears, no outputs or errors) and doing Hosts -> Actions -> All Hosts -> Stop All Components fails with the following exception:
> {code}2015-11-19 09:59:59,893 - Execution of 'mysql -u root --password=<password> -h <fqdn>  -s -e "select version();"' returned 1. ERROR 2003 (HY000): Can't connect to MySQL server on '<fqdn>' (111)
> Traceback (most recent call last):
>   File "/var/lib/ambari-agent/cache/common-services/RANGER/0.4.0/package/scripts/ranger_admin.py", line 124, in <module>
>     RangerAdmin().execute()
>   File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 218, in execute
>     method(env)
>   File "/var/lib/ambari-agent/cache/common-services/RANGER/0.4.0/package/scripts/ranger_admin.py", line 45, in install
>     self.configure(env)
>   File "/var/lib/ambari-agent/cache/common-services/RANGER/0.4.0/package/scripts/ranger_admin.py", line 103, in configure
>     ranger('ranger_admin')
>   File "/var/lib/ambari-agent/cache/common-services/RANGER/0.4.0/package/scripts/setup_ranger.py", line 28, in ranger
>     setup_ranger_admin()
>   File "/var/lib/ambari-agent/cache/common-services/RANGER/0.4.0/package/scripts/setup_ranger.py", line 36, in setup_ranger_admin
>     check_db_connnection()
>   File "/var/lib/ambari-agent/cache/common-services/RANGER/0.4.0/package/scripts/setup_ranger.py", line 110, in check_db_connnection
>     raise Fail('Ranger Database connection check failed')
> resource_management.core.exceptions.Fail: Ranger Database connection check failed
> {code}
> This is a bug when Ambari is in a state where it's unable to control it's services. I worked around it for now by removing the Ranger service via the API until I have time to come back and properly redeploy it later.
> Technically I can understand something failing the underlying database check for a single service, but I've noticed that Ambari has a lot of fringe conditions around state and having an installed but unconfigured service breaks it.
> Also there should never be a scenario where Start All does absolutely nothing and doesn't feed back to the user in any way.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)