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 60051200D62 for ; Fri, 1 Dec 2017 20:10:10 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 5E98B160BF4; Fri, 1 Dec 2017 19:10:10 +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 7EEF0160C06 for ; Fri, 1 Dec 2017 20:10:09 +0100 (CET) Received: (qmail 61249 invoked by uid 500); 1 Dec 2017 19:10:08 -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 61224 invoked by uid 99); 1 Dec 2017 19:10:08 -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; Fri, 01 Dec 2017 19:10:08 +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 E83C21808A5 for ; Fri, 1 Dec 2017 19:10:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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-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 54WV4q2dLq34 for ; Fri, 1 Dec 2017 19:10:06 +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 368125FB30 for ; Fri, 1 Dec 2017 19:10:05 +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 B3C99E25B0 for ; Fri, 1 Dec 2017 19:10: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 35B3B255E5 for ; Fri, 1 Dec 2017 19:10:02 +0000 (UTC) Date: Fri, 1 Dec 2017 19:10:02 +0000 (UTC) From: "Di Li (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-22574) Failed to restart services on PPC cluster post Ambari upgrade for IOP/HDP migration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 01 Dec 2017 19:10:10 -0000 [ https://issues.apache.org/jira/browse/AMBARI-22574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22574: --------------------------- Description: The cluster started as IOP 4.2.5 on PPC with NameNode HA enabled. I upgraded Ambari to Ambari 2.6.1. The NN HA setting does not matter to the issue. After the Ambari upgrade, I can't restart services by clicking the "Restart" button on each service with that "restart needed" icon. Nor can I abort the requests. Ambari server log contains the following error on unable to find redhat-ppc7 os type. java.lang.RuntimeException: org.apache.ambari.server.controller.spi.SystemException: Operating System matching redhat-ppc7 could not be found at org.apache.ambari.server.actionmanager.ExecutionCommandWrapper.getExecutionCommand(ExecutionCommandWrapper.java:253) at org.apache.ambari.server.actionmanager.ActionScheduler.abortOperationsForStage(ActionScheduler.java:880) at org.apache.ambari.server.actionmanager.ActionScheduler.processCancelledRequestsList(ActionScheduler.java:1172) at org.apache.ambari.server.actionmanager.ActionScheduler.doWork(ActionScheduler.java:333) at org.apache.ambari.server.actionmanager.ActionScheduler.run(ActionScheduler.java:310) at java.lang.Thread.run(Thread.java:748) Caused by: org.apache.ambari.server.controller.spi.SystemException: Operating System matching redhat-ppc7 could not be found at org.apache.ambari.server.state.stack.upgrade.RepositoryVersionHelper.getOSEntityForHost(RepositoryVersionHelper.java:422) at org.apache.ambari.server.actionmanager.ExecutionCommandWrapper.getExecutionCommand(ExecutionCommandWrapper.java:247) repo_version table had "redhat7" as the os type in the repository information. I worked around the issue by updating repo_version table to have redhat-ppc7 as the os type via the following SQL query: update repo_version set repositories='[{"OperatingSystems/ambari_managed_repositories":"true","repositories":[{"Repositories/repo_id":"IOP-4.2.5","Repositories/base_url":"http://birepo-build.svl.ibm.com/repos/IOP/RHEL7/ppc64le/4.2.5.0/20170602_1749","Repositories/repo_name":"IOP"},{"Repositories/repo_id":"IOP-UTILS-1.3","Repositories/base_url":"http://birepo-build.svl.ibm.com/repos/IOP-UTILS/RHEL7/ppc64le/1.3","Repositories/repo_name":"IOP-UTILS"}],"OperatingSystems/os_type":"redhat-ppc7"}]' where repo_version_id = 1; was: The cluster started as IOP 4.2.5 on PPC with NameNode HA enabled. I upgraded Ambari to Ambari 2.6.1 (build id 85). The NN HA setting does not matter to the issue. After the Ambari upgrade, I can't restart services by clicking the "Restart" button on each service with that "restart needed" icon. Nor can I abort the requests. Ambari server log contains the following error on unable to find redhat-ppc7 os type. java.lang.RuntimeException: org.apache.ambari.server.controller.spi.SystemException: Operating System matching redhat-ppc7 could not be found at org.apache.ambari.server.actionmanager.ExecutionCommandWrapper.getExecutionCommand(ExecutionCommandWrapper.java:253) at org.apache.ambari.server.actionmanager.ActionScheduler.abortOperationsForStage(ActionScheduler.java:880) at org.apache.ambari.server.actionmanager.ActionScheduler.processCancelledRequestsList(ActionScheduler.java:1172) at org.apache.ambari.server.actionmanager.ActionScheduler.doWork(ActionScheduler.java:333) at org.apache.ambari.server.actionmanager.ActionScheduler.run(ActionScheduler.java:310) at java.lang.Thread.run(Thread.java:748) Caused by: org.apache.ambari.server.controller.spi.SystemException: Operating System matching redhat-ppc7 could not be found at org.apache.ambari.server.state.stack.upgrade.RepositoryVersionHelper.getOSEntityForHost(RepositoryVersionHelper.java:422) at org.apache.ambari.server.actionmanager.ExecutionCommandWrapper.getExecutionCommand(ExecutionCommandWrapper.java:247) repo_version table had "redhat7" as the os type in the repository information. I worked around the issue by updating repo_version table to have redhat-ppc7 as the os type via the following SQL query: update repo_version set repositories='[{"OperatingSystems/ambari_managed_repositories":"true","repositories":[{"Repositories/repo_id":"IOP-4.2.5","Repositories/base_url":"http://birepo-build.svl.ibm.com/repos/IOP/RHEL7/ppc64le/4.2.5.0/20170602_1749","Repositories/repo_name":"IOP"},{"Repositories/repo_id":"IOP-UTILS-1.3","Repositories/base_url":"http://birepo-build.svl.ibm.com/repos/IOP-UTILS/RHEL7/ppc64le/1.3","Repositories/repo_name":"IOP-UTILS"}],"OperatingSystems/os_type":"redhat-ppc7"}]' where repo_version_id = 1; > Failed to restart services on PPC cluster post Ambari upgrade for IOP/HDP migration > ----------------------------------------------------------------------------------- > > Key: AMBARI-22574 > URL: https://issues.apache.org/jira/browse/AMBARI-22574 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.6.1 > Reporter: Di Li > Priority: Critical > Fix For: 2.6.1 > > > The cluster started as IOP 4.2.5 on PPC with NameNode HA enabled. I upgraded Ambari to Ambari 2.6.1. The NN HA setting does not matter to the issue. > After the Ambari upgrade, I can't restart services by clicking the "Restart" button on each service with that "restart needed" icon. Nor can I abort the requests. > Ambari server log contains the following error on unable to find redhat-ppc7 os type. > java.lang.RuntimeException: org.apache.ambari.server.controller.spi.SystemException: Operating System matching redhat-ppc7 could not be found > at org.apache.ambari.server.actionmanager.ExecutionCommandWrapper.getExecutionCommand(ExecutionCommandWrapper.java:253) > at org.apache.ambari.server.actionmanager.ActionScheduler.abortOperationsForStage(ActionScheduler.java:880) > at org.apache.ambari.server.actionmanager.ActionScheduler.processCancelledRequestsList(ActionScheduler.java:1172) > at org.apache.ambari.server.actionmanager.ActionScheduler.doWork(ActionScheduler.java:333) > at org.apache.ambari.server.actionmanager.ActionScheduler.run(ActionScheduler.java:310) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.apache.ambari.server.controller.spi.SystemException: Operating System matching redhat-ppc7 could not be found > at org.apache.ambari.server.state.stack.upgrade.RepositoryVersionHelper.getOSEntityForHost(RepositoryVersionHelper.java:422) > at org.apache.ambari.server.actionmanager.ExecutionCommandWrapper.getExecutionCommand(ExecutionCommandWrapper.java:247) > repo_version table had "redhat7" as the os type in the repository information. I worked around the issue by updating repo_version table to have redhat-ppc7 as the os type via the following SQL query: > update repo_version set repositories='[{"OperatingSystems/ambari_managed_repositories":"true","repositories":[{"Repositories/repo_id":"IOP-4.2.5","Repositories/base_url":"http://birepo-build.svl.ibm.com/repos/IOP/RHEL7/ppc64le/4.2.5.0/20170602_1749","Repositories/repo_name":"IOP"},{"Repositories/repo_id":"IOP-UTILS-1.3","Repositories/base_url":"http://birepo-build.svl.ibm.com/repos/IOP-UTILS/RHEL7/ppc64le/1.3","Repositories/repo_name":"IOP-UTILS"}],"OperatingSystems/os_type":"redhat-ppc7"}]' where repo_version_id = 1; -- This message was sent by Atlassian JIRA (v6.4.14#64029)