Di Li created AMBARI-21625:
------------------------------
Summary: 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
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)
