[jira] [Commented] (AMBARI-21625) Failed to update custom repos defined via service extension after such a service is installed to cluster

["Balázs Bence Sári (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-21625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112657#comment-16112657 ] 

Balázs Bence Sári commented on AMBARI-21625:
--------------------------------------------

Hey [~dili], extension repo's were addressed by AMBARI-15538, but may not have been tested with stack upgrades.

If I interpret the report well these are the steps to reproduce:
1. Install Ambari 2.5.2 and HDP 2.5.1
3. register an extension service
2. add an instance of the extension service to the cluster
3. remove extension service instance from the cluster
4. EU to HDP 2.5.2
5. upgrade extension (does this mean simply registering a new version? - I am not familiar with dealing with extensions)
6. (fails at this point) try to re-add extension service instance to the cluster.

Could you confirm this is the case or correct?

> 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ázs Bence Sári
>             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 hit 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: 
> An internal syste
> m exception occurred: Stack data, stackName=HDP, stackVersion= 2.5, osType=redhat7,
>  repoId= IBM-Big_SQL
> Via REST API: 
> {
>   "status" : 404,
>   "message" : "org.apache.ambari.server.controller.spi.NoSuchResourceException: The specified resource doesn't exist: Stack data, stackName=HDP, stackVersion= 2.5, osType=redhat7, repoId= IBM-Big_SQL"
> }```
> *Investigation*: Ambari server failed to reads BigSQL's repoinfo.xml  (defined 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. It only reads repo ids defined in /var/lib/ambari-server/resources/stacks/HDP/2.6/repos/repoinfo.xml



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