You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2025/04/14 23:27:01 UTC
[jira] [Updated] (AMBARI-23350) ServiceConfig API call uses "MpackName-Vesion" for SG instead of just "MpackName".
[ https://issues.apache.org/jira/browse/AMBARI-23350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wei-Chiu Chuang updated AMBARI-23350:
-------------------------------------
Fix Version/s: 3.1.0
(was: 3.0.0)
> ServiceConfig API call uses "MpackName-Vesion" for SG instead of just "MpackName".
> ----------------------------------------------------------------------------------
>
> Key: AMBARI-23350
> URL: https://issues.apache.org/jira/browse/AMBARI-23350
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-web
> Reporter: Swapan Shridhar
> Assignee: Swapan Shridhar
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.1.0
>
> Attachments: Screen Shot 2018-03-23 at 1.05.13 PM.png
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> 1. ServiceConfig API call uses "MpackName-Vesion" for SG instead of just "MpackName".
> - With "[AMBARI-23269] Removed mpack version from service group name (#692)" we have started using just the *Mpack* Name to create the SG.
> - But we haven't updated the Service Configs API POST calls, which still continue to use *MpackName-Vesion* for referring SG. This needs to be updated.
> Failure :
> POST http://<Server>:8080/api/v1/clusters/c1/servicegroups/HDPCORE-1.0.0-b140/services/HDFS/configurations
> [^Screen Shot 2018-03-23 at 1.05.13 PM.png]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ambari.apache.org
For additional commands, e-mail: issues-help@ambari.apache.org