You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2017/09/12 12:51:00 UTC
[jira] [Commented] (AMBARI-21928) In case if component package
doesn't advertise his version, Ambari silently failing on deploy stack
steps
[ https://issues.apache.org/jira/browse/AMBARI-21928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162882#comment-16162882 ]
Hudson commented on AMBARI-21928:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #194 (See [https://builds.apache.org/job/Ambari-branch-2.6/194/])
AMBARI-21928 In case if component package doesn't advertise his version, (hapylestat: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e7e58bbf473c25558e5dd952cf8c81115876eba9])
* (edit) ambari-common/src/main/python/resource_management/libraries/functions/stack_tools.py
* (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/shared_initialization.py
* (edit) ambari-common/src/main/python/resource_management/libraries/functions/version_select_util.py
* (edit) ambari-common/src/main/python/resource_management/libraries/script/script.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/hooks/after-INSTALL/test_after_install.py
> In case if component package doesn't advertise his version, Ambari silently failing on deploy stack steps
> ---------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-21928
> URL: https://issues.apache.org/jira/browse/AMBARI-21928
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.6.0
> Reporter: Dmytro Grinenko
> Assignee: Dmytro Grinenko
> Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21928-branch26.patch, AMBARI-21928.patch
>
>
> In case if component didn't advertise version using stack selecting tool, some Ambari operations may fail with weird exceptions, what may be misleading.
> We should add log information with strictly pointing to this issue
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)