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

Hudson commented on AMBARI-13309:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #3596 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3596/])
AMBARI-13309. After hdp-select failure Ambari won't retry resulting in 
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cad57c562692ac7bc8c61a3d4504a8c12fdae2f0])
* 
ambari-server/src/test/python/stacks/2.0.6/hooks/after-INSTALL/test_after_install.py
* 
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/shared_initialization.py


> After hdp-select failure Ambari won't retry resulting in most components 
> failures with strange output
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13309
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13309
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.2.0
>
>
> STR:  
> 1\. I had hdp-select failed due to env issue
>     
>     
>     resource_management.core.exceptions.Fail: Execution of 'ambari-sudo.sh  
> -H -E touch /var/lib/ambari-agent/data/hdp-select-set-all.performed ; 
> ambari-sudo.sh /usr/bin/hdp-select set all `ambari-python-wrap 
> /usr/bin/hdp-select versions | grep ^2.2 | tail -1`' returned 1. Traceback 
> (most recent call last):
>       File "/usr/bin/hdp-select", line 363, in ?
>         setPackages(pkgs, args[2], options.rpm_mode)
>       File "/usr/bin/hdp-select", line 256, in setPackages
>         os.symlink(target + "/" + leaves[pkg], linkname)
>     OSError: [Errno 17] File exists
>     
> 2\. I went and fixed the issue with my env  
> 3\. But Ambari didn't try again to run hdp-select again and attempt to start
> all the components, most of them failed with different strange error messages,
> which would be really hard to understand for a user.



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

Reply via email to