You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2016/03/18 19:13:33 UTC

[jira] [Commented] (AMBARI-15461) Yarn start is failed (YARN Client Install) after upgrade from 1.7.0 to 2.2.2.0

    [ https://issues.apache.org/jira/browse/AMBARI-15461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201900#comment-15201900 ] 

Andrew Onischuk commented on AMBARI-15461:
------------------------------------------

Currently Hadoop QA has large queue and it takes too long to get tests results, tested locally:
{noformat}
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Ambari Main ....................................... SUCCESS [3.980s]
[INFO] Apache Ambari Project POM ......................... SUCCESS [0.110s]
[INFO] Ambari Web ........................................ SUCCESS [38.507s]
[INFO] Ambari Views ...................................... SUCCESS [20.587s]
[INFO] ambari-metrics .................................... SUCCESS [0.871s]
[INFO] Ambari Metrics Common ............................. SUCCESS [2.611s]
[INFO] Ambari Server ..................................... SUCCESS [1:42.546s]
[INFO] Ambari Agent ...................................... SUCCESS [21.630s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3:11.586s
[INFO] Finished at: Fri Mar 18 17:58:37 EET 2016
[INFO] Final Memory: 82M/1076M
[INFO] ------------------------------------------------------------------------
{noformat}

> 	Yarn start is failed (YARN Client Install) after upgrade from 1.7.0 to 2.2.2.0
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-15461
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15461
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15461.patch
>
>
> STR: *<http://172.22.116.102:8080/#/main/services/YARN/summary*>  
> 1)Deploy old version  
> 2)Enable/Disable MIT security  
> 3)Make Ambari only Upgrade
> **Actual result:**  
> Yarn start is failed (YARN Client Install) after upgrade from 1.7.0 to 2.2.2.0
>     
>     
>     
>     stderr:   /var/lib/ambari-agent/data/errors-1125.txt
>     
>     Traceback (most recent call last):
>       File "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/yarn_client.py", line 65, in <module>
>         YarnClient().execute()
>       File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 219, in execute
>         method(env)
>       File "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/yarn_client.py", line 34, in install
>         self.configure(env)
>       File "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/yarn_client.py", line 37, in configure
>         import params
>       File "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params.py", line 28, in <module>
>         from params_linux import *
>       File "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py", line 142, in <module>
>         rm_https_port = config['configurations']['yarn-site']['yarn.resourcemanager.webapp.https.address'].split(':')[-1]
>       File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py", line 81, in __getattr__
>         raise Fail("Configuration parameter '" + self.name + "' was not found in configurations dictionary!")
>     resource_management.core.exceptions.Fail: Configuration parameter 'yarn.resourcemanager.webapp.https.address' was not found in configurations dictionary!
>     



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