Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 2 Aug 2017 23:15:02 +0000 (UTC)
From: "Siddharth Wagle (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13091633.1501611088000.79107.1501715702749@Atlassian.JIRA>
In-Reply-To: <JIRA.13091633.1501611088000@Atlassian.JIRA>
References: <JIRA.13091633.1501611088000@Atlassian.JIRA> <JIRA.13091633.1501611088708@jira-lw-us.apache.org>
Subject: [jira] [Assigned] (AMBARI-21625) Failed to update custom repos
 defined via service extension after such a service is installed to cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 02 Aug 2017 23:15:09 -0000


     [ https://issues.apache.org/jira/browse/AMBARI-21625?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Siddharth Wagle reassigned AMBARI-21625:
----------------------------------------

    Assignee: Bal=C3=A1zs Bence S=C3=A1ri

> Failed to update custom repos defined via service extension after such a =
service is installed to cluster
> -------------------------------------------------------------------------=
-------------------------------
>
>                 Key: AMBARI-21625
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21625
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.2
>            Reporter: Di Li
>            Assignee: Bal=C3=A1zs Bence S=C3=A1ri
>             Fix For: 2.5.2
>
>
> This should be a general issue that can be reproduced by having a service=
 as an extension. add it to an HDP 2.6.2/Ambari 2.5.2 cluster, then try to =
update repos for the HDP 2.6.2 stack.
> Our QA hit on BigSQL, but it doesn't have to be BigSQL to reproduce.
> Our QA hit the following error on HDP/HDP upgrade ( will most likely to h=
it it also on the migration):
> *Case* HDP 2.4/BigSQL 4.2.5 upgrade to HDP 2.5.1/BigSQL 5.0.1
> *Error* Updating BigSQL URL via UI and via REST API throws errors, after =
adding BigSQL back to the cluster  post HDP 2.5.1 EU.
> ```Via UI: The validation will fail with ambari server side error:=20
> An internal syste
> m exception occurred: Stack data, stackName=3DHDP, stackVersion=3D 2.5, o=
sType=3Dredhat7,
>  repoId=3D IBM-Big_SQL
> Via REST API:=20
> {
>   "status" : 404,
>   "message" : "org.apache.ambari.server.controller.spi.NoSuchResourceExce=
ption: The specified resource doesn't exist: Stack data, stackName=3DHDP, s=
tackVersion=3D 2.5, osType=3Dredhat7, repoId=3D IBM-Big_SQL"
> }```
> *Investigation*: Ambari server failed to reads BigSQL's repoinfo.xml  (de=
fined as part of the extension /var/lib/ambari-server/resources/extensions/=
IBM-Big_SQL/5.0.1.0/services/BIGSQL/repos/repoinfo.xml ) for the repo id. I=
t only reads repo ids defined in /var/lib/ambari-server/resources/stacks/HD=
P/2.6/repos/repoinfo.xml


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