ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-12999) Make link creation upgrade compatible, because after upgrade, Storm start fails
Date Thu, 03 Sep 2015 17:48:46 GMT

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

Hudson commented on AMBARI-12999:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #3382 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3382/])
AMBARI-12999. Make link creation upgrade compatible, because after upgrade, Storm start fails.(vbrodetskyi)
(vbrodetskyi: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8af7df30ea5e966c5d137f5fb53221ba9b2e046b)
* ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/storm.py


> Make link creation upgrade compatible, because after upgrade, Storm start fails
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-12999
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12999
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.1.2
>
>         Attachments: AMBARI-12999.patch
>
>
> During the upgrade of 2.1 to 2.3 testing we noticed that Storm services will not start
due to a bad symlink operation. This operation fails because we use a wildcard in the symlink,
and this has more than one match forcing ln to expect the destination to be a directory.



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

Mime
View raw message