From issues-return-66771-archive-asf-public=cust-asf.ponee.io@ambari.apache.org Thu Feb 15 13:00:12 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 59D0218064A for ; Thu, 15 Feb 2018 13:00:12 +0100 (CET) Received: (qmail 73101 invoked by uid 500); 15 Feb 2018 12:00:11 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 73092 invoked by uid 99); 15 Feb 2018 12:00:11 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Feb 2018 12:00:11 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id DB28A180493 for ; Thu, 15 Feb 2018 12:00:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.811 X-Spam-Level: X-Spam-Status: No, score=-109.811 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id XjS2xmf1_0q8 for ; Thu, 15 Feb 2018 12:00:10 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id CAF2A5F3D1 for ; Thu, 15 Feb 2018 12:00:09 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E1108E00A6 for ; Thu, 15 Feb 2018 12:00:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1C3F421E5A for ; Thu, 15 Feb 2018 12:00:00 +0000 (UTC) Date: Thu, 15 Feb 2018 12:00:00 +0000 (UTC) From: "Hudson (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-22986) Not able to add Livy2 after doing rolling upgrade to M21 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-22986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365439#comment-16365439 ] Hudson commented on AMBARI-22986: --------------------------------- FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #611 (See [https://builds.apache.org/job/Ambari-branch-2.6/611/]) AMBARI-22986. Not able to add Livy2 after doing rolling upgrade to M21 (dlysnichenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=16bbca3784b6a40d0c2b26083882fa2bed970972]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog262.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java AMBARI-22986. Not able to add Livy2 after doing rolling upgrade to M21 - (dlysnichenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=c3ee12154760d3887d806f646963f96785e1928c]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog262.java AMBARI-22986. Not able to add Livy2 after doing rolling upgrade to M21 - (dlysnichenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=e2e462934c38dfcd9593faaf9bdadc0ace5f5350]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java > Not able to add Livy2 after doing rolling upgrade to M21 > -------------------------------------------------------- > > Key: AMBARI-22986 > URL: https://issues.apache.org/jira/browse/AMBARI-22986 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.6.1 > Reporter: Dmitry Lysnichenko > Assignee: Dmitry Lysnichenko > Priority: Blocker > Fix For: 2.6.2 > > > Steps to reproduce : > 1) Create a cluster with ambari-2.4.3+HDP-2.5.3 > 2) Do ambari upgrade to ambari-2.6.1 > 3) Do stack upgrade to HDP-2.6.4 > After upgrade its not possible to add livy2(Livy2 is a spark2 component). > This issue is specific to rolling upgrade. I am able to add livy2 in express upgraded cluster > Also in EU cluster I see 'Upgrade service configs' step , this step is likely updating the spark2 livy2 configs. But I am not seeing this in RU cluster. > The reason is that the desired version of a cluster is not updated (only during cross-stack rolling upgrade) -- This message was sent by Atlassian JIRA (v7.6.3#76005)