Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6A6B8200CDE for ; Tue, 8 Aug 2017 18:18:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 68EC016782C; Tue, 8 Aug 2017 16:18:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id ADB92167829 for ; Tue, 8 Aug 2017 18:18:03 +0200 (CEST) Received: (qmail 46347 invoked by uid 500); 8 Aug 2017 16:18:02 -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 46338 invoked by uid 99); 8 Aug 2017 16:18:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Aug 2017 16:18:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 736701A0507 for ; Tue, 8 Aug 2017 16:18:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id V5VkkQPe7GQu for ; Tue, 8 Aug 2017 16:18:01 +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 16D4E5FC3A for ; Tue, 8 Aug 2017 16:18: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 68713E0051 for ; Tue, 8 Aug 2017 16:18:00 +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 21AD223FFD for ; Tue, 8 Aug 2017 16:18:00 +0000 (UTC) Date: Tue, 8 Aug 2017 16:18:00 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-21679) Service Checks Will Run Multiple Times In Patch/Service Upgrades MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 08 Aug 2017 16:18:04 -0000 [ https://issues.apache.org/jira/browse/AMBARI-21679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118555#comment-16118555 ] Hadoop QA commented on AMBARI-21679: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12880846/AMBARI-21679.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/11957//console This message is automatically generated. > Service Checks Will Run Multiple Times In Patch/Service Upgrades > ---------------------------------------------------------------- > > Key: AMBARI-21679 > URL: https://issues.apache.org/jira/browse/AMBARI-21679 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Reporter: Nate Cole > Assignee: Nate Cole > Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21679.patch > > > There are two issues with Service Checks and patches: > 1. A service check grouping can be orchestrated one right after the other if the grouping in between them has no processing. > 2. A service check grouping can be orchestrated before any components have been scheduled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)