ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21595) Ambari Server Setup Code Fails Because of Missing Stack Upgrade
Date Fri, 28 Jul 2017 09:15:00 GMT

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

Hadoop QA commented on AMBARI-21595:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12879320/AMBARI-21595.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11884//console

This message is automatically generated.

> Ambari Server Setup Code Fails Because of Missing Stack Upgrade
> ---------------------------------------------------------------
>
>                 Key: AMBARI-21595
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21595
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>            Priority: Blocker
>             Fix For: 2.6.0
>
>         Attachments: AMBARI-21595.patch
>
>
> On {{branch-feature-AMBARI-21450}}, there is a Python failure on ambari-server setup:
> {code}
> Using python  /usr/bin/python
> Setup ambari-server
> Traceback (most recent call last):
> File "/usr/sbin/ambari-server.py", line 40, in <module>
> from ambari_server.serverUpgrade import upgrade, upgrade_stack, set_current
> ImportError: cannot import name upgrade_stack
> {code}
> This is most likely a cherry-pick issue from trunk where all "upgrade stack" code was
removed. I think that we should also remove it from here as well since this will cause problems
with PATCH repositories anyway.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message