[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
]
Swapan Shridhar updated AMBARI-23350:
-
Description:
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://: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]
was:
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://: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]
*2. POST host API calls fail as HostResourceProvider has few member variables
uninitialized.*
*Issue:*
POST http://172.22.65.77:8080/api/v1/clusters/c1/hosts returns 500.
*Reason:*
Stack Trace:
{code:title=ambari-server.log}
java.lang.NullPointerException
at
org.apache.ambari.server.controller.internal.HostResourceProvider.createHosts(HostResourceProvider.java:588)
at
org.apache.ambari.server.controller.internal.HostResourceProvider$1.invoke(HostResourceProvider.java:255)
at
org.apache.ambari.server.controller.internal.HostResourceProvider$1.invoke(HostResourceProvider.java:252)
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:465)
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:288)
at
org.apache.ambari.server.controller.internal.HostResourceProvider.createResourcesAuthorized(HostResourceProvider.java:252)
at
org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:231)
{code}
*Code Line:*
{code:title=https://github.com/apache/ambari/blob/branch-feature-AMBARI-14714/ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostResourceProvider.java#L575}
HostLevelParamsUpdateEvent hostLevelParamsUpdateEvent = new
HostLevelParamsUpdateEvent(clusterId, new HostLevelParamsCluster(
getManagementController().retrieveHostRepositories(cl, addedHost),
recoveryConfigHelper.getRecoveryConfig(cl.getClusterName(),
addedHost.getHostName())
));
{code}
NPE is because *recoveryConfigHelper* is not initialized. Further,
*hostLevelParamsHolder* and *topologyHolder* are also null.
> 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.0.0
>
> Attachments: Screen Shot 2018-03-23 at 1.05.13 PM.png
>
> Time Spent: 0.5h
> 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://: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
(v7.6.3#76005)
[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
]
Swapan Shridhar updated AMBARI-23350:
-
Summary: ServiceConfig API call uses "MpackName-Vesion" for SG instead of
just "MpackName". (was: Issues: 1. ServiceConfig API call uses
"MpackName-Vesion" for SG instead of just "MpackName". 2. POST host API calls
fail as HostResourceProvider has few member variables uninitialized.)
> 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.0.0
>
> Attachments: Screen Shot 2018-03-23 at 1.05.13 PM.png
>
> Time Spent: 0.5h
> 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://: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]
> *2. POST host API calls fail as HostResourceProvider has few member variables
> uninitialized.*
> *Issue:*
> POST http://172.22.65.77:8080/api/v1/clusters/c1/hosts returns 500.
> *Reason:*
> Stack Trace:
> {code:title=ambari-server.log}
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider.createHosts(HostResourceProvider.java:588)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider$1.invoke(HostResourceProvider.java:255)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider$1.invoke(HostResourceProvider.java:252)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:465)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:288)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider.createResourcesAuthorized(HostResourceProvider.java:252)
> at
> org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:231)
> {code}
> *Code Line:*
> {code:title=https://github.com/apache/ambari/blob/branch-feature-AMBARI-14714/ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostResourceProvider.java#L575}
> HostLevelParamsUpdateEvent hostLevelParamsUpdateEvent = new
> HostLevelParamsUpdateEvent(clusterId, new HostLevelParamsCluster(
> getManagementController().retrieveHostRepositories(cl, addedHost),
> recoveryConfigHelper.getRecoveryConfig(cl.getClusterName(),
> addedHost.getHostName())
> ));
> {code}
> NPE is because *recoveryConfigHelper* is not initialized. Further,
> *hostLevelParamsHolder* and *topologyHolder* are also null.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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
]
Swapan Shridhar updated AMBARI-23350:
-
Description:
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://: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]
*2. POST host API calls fail as HostResourceProvider has few member variables
uninitialized.*
*Issue:*
POST http://172.22.65.77:8080/api/v1/clusters/c1/hosts returns 500.
*Reason:*
Stack Trace:
{code:title=ambari-server.log}
java.lang.NullPointerException
at
org.apache.ambari.server.controller.internal.HostResourceProvider.createHosts(HostResourceProvider.java:588)
at
org.apache.ambari.server.controller.internal.HostResourceProvider$1.invoke(HostResourceProvider.java:255)
at
org.apache.ambari.server.controller.internal.HostResourceProvider$1.invoke(HostResourceProvider.java:252)
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:465)
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:288)
at
org.apache.ambari.server.controller.internal.HostResourceProvider.createResourcesAuthorized(HostResourceProvider.java:252)
at
org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:231)
{code}
*Code Line:*
{code:title=https://github.com/apache/ambari/blob/branch-feature-AMBARI-14714/ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostResourceProvider.java#L575}
HostLevelParamsUpdateEvent hostLevelParamsUpdateEvent = new
HostLevelParamsUpdateEvent(clusterId, new HostLevelParamsCluster(
getManagementController().retrieveHostRepositories(cl, addedHost),
recoveryConfigHelper.getRecoveryConfig(cl.getClusterName(),
addedHost.getHostName())
));
{code}
NPE is because *recoveryConfigHelper* is not initialized. Further,
*hostLevelParamsHolder* and *topologyHolder* are also null.
was:
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://: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]
> 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
> Fix For: 3.0.0
>
> Attachments: Screen Shot 2018-03-23 at 1.05.13 PM.png
>
>
> 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://: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]
> *2. POST host API calls fail as HostResourceProvider has few member variables
> uninitialized.*
> *Issue:*
> POST http://172.22.65.77:8080/api/v1/clusters/c1/hosts returns 500.
> *Reason:*
> Stack Trace:
> {code:title=ambari-server.log}
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider.createHosts(HostResourceProvider.java:588)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider$1.invoke(HostResourceProvider.java:255)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider$1.invoke(HostResourceProvider.java:252)
> at
>
[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 ] Swapan Shridhar updated AMBARI-23350: - Description: 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://: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] was: 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://: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|thumbnail! > 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 > Fix For: 3.0.0 > > Attachments: Screen Shot 2018-03-23 at 1.05.13 PM.png > > > 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://: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 (v7.6.3#76005)
[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 ] Swapan Shridhar updated AMBARI-23350: - Attachment: Screen Shot 2018-03-23 at 1.05.13 PM.png > 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 > Fix For: 3.0.0 > > Attachments: Screen Shot 2018-03-23 at 1.05.13 PM.png > > > 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://: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|thumbnail! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 ] Swapan Shridhar updated AMBARI-23350: - Description: 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://: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|thumbnail! > 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 > Fix For: 3.0.0 > > Attachments: Screen Shot 2018-03-23 at 1.05.13 PM.png > > > 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://: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|thumbnail! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
