From issues-return-67610-archive-asf-public=cust-asf.ponee.io@ambari.apache.org Wed Feb 28 17:52:06 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 6A328180671 for ; Wed, 28 Feb 2018 17:52:05 +0100 (CET) Received: (qmail 72553 invoked by uid 500); 28 Feb 2018 16:52:04 -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 72537 invoked by uid 99); 28 Feb 2018 16:52:04 -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; Wed, 28 Feb 2018 16:52:04 +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 797BB1805CD for ; Wed, 28 Feb 2018 16:52:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, 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-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id NFH8tMJdL262 for ; Wed, 28 Feb 2018 16:52:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id E98E25F640 for ; Wed, 28 Feb 2018 16:52:01 +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 2F6C0E093B for ; Wed, 28 Feb 2018 16:52:01 +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 87A0A2411A for ; Wed, 28 Feb 2018 16:52:00 +0000 (UTC) Date: Wed, 28 Feb 2018 16:52:00 +0000 (UTC) From: "Dmitry Lysnichenko (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-23110) livy2-client version is not updated as part of Patch Upgrade. 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-23110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-23110: ---------------------------------------- Fix Version/s: 2.6.2 > livy2-client version is not updated as part of Patch Upgrade. > ------------------------------------------------------------- > > Key: AMBARI-23110 > URL: https://issues.apache.org/jira/browse/AMBARI-23110 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.6.2 > Reporter: Dmitry Lysnichenko > Assignee: Dmitry Lysnichenko > Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 20m > Remaining Estimate: 0h > > *STR* > 1) Deployed cluster with Ambari version: 2.6.1.0-143 and HDP version: 2.6.4.0-91 > 2) Upgrade Ambari to Target Version: 2.6.2.0-67 > 3) Patch Express Upgrade Spark2 to HDP-2.6.5.0-120 > Observe the version of livy2-client after PU > result of hdp-select command > {code:java} > [root@ctr-e138-1518143905142-45389-01-000002 ~]# hdp-select | grep livy2-client > livy2-client - 2.6.4.0-91 > [root@ctr-e138-1518143905142-45389-01-000002 ~]# > {code} > hdp-select outputs > {code:java} > ===6=== > livy2-client - 2.6.4.0-91 > livy2-server - 2.6.5.0-120 > ===2=== > livy2-client - 2.6.4.0-91 > livy2-server - 2.6.4.0-91 > ===5=== > livy2-client - 2.6.4.0-91 > livy2-server - 2.6.4.0-91 > ===4=== > livy2-client - 2.6.4.0-91 > livy2-server - 2.6.4.0-91 > {code} > *Note : The livy2-client version was set correctly during Full stack Express Upgrade. The issue is seen only for Patch Upgrade* > LIVY2_CLIENT isn't actually a component which Ambari manages. That's why it's never orchestrated. I suppose that we can fix this by having the SPARK2_CLIENT also update the pointers for LIVY2_CLIENT by changing the stack_packages.json. -- This message was sent by Atlassian JIRA (v7.6.3#76005)