[
https://issues.apache.org/jira/browse/AMBARI-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-4455:
---------------------------------
Attachment: AMBARI-4455.patch
> Failure saving configuration in a new Host Config Group
> -------------------------------------------------------
>
> Key: AMBARI-4455
> URL: https://issues.apache.org/jira/browse/AMBARI-4455
> Project: Ambari
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.3
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Blocker
> Fix For: 1.4.4
>
> Attachments: AMBARI-4455.patch, AMBARI-4455_branch-1.4.4.patch
>
>
> 1) Clean install, new cluster, HDP 1.3.3 stack
> 2) using Ambari 1.4.3
> 3) Two nodes (one with NN, other with SNN) -- both with DN, TT
> 4) create new HDFS group, put a host in the group, click save
> 5) You return to Ambari with that new group set as the group.
> 6) Filter to find a prop
> 7) Override one property
> 8) Click save, failure message
> Saw PUT error. Attaching screen shots.
> The issue is reproducible based on Step 5. Seems if you create a new group
> and save, when that group is set in the UI and you try to save, it PUTs the
> config_group w/o the id, causing the PUT failure.
> /api/v1/clusters/MyCluster/config_groups/ is being called and not
> /api/v1/clusters/MyCluster/config_groups/*\{id}* (id is not set)
> I have seen that PUT failure surface as "failure to save" message as well as
> "silent failure" where the message says successfully saved but the PUT failed
> under-the-hood.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
