You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Andrii Tkach (JIRA)" <ji...@apache.org> on 2018/02/05 14:23:00 UTC

[jira] [Updated] (AMBARI-22912) Host details page: components not reconfigured after deleting their host

     [ https://issues.apache.org/jira/browse/AMBARI-22912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrii Tkach updated AMBARI-22912:
----------------------------------
    Description: 
# When deleting a host, after components deletion config changes not triggered, as opposed to when they removed individually.
 # When adding/deleting component config modification triggered before actual call to add/delete a component, so even if the call fails then configs would be modified

  was:
# When deleting a host, after components deletion config changes not triggered, as opposed to when they removed individually.
# When adding/deleting component config modification triggered before actual call to add/delete a component, so if the call fails then configs would be modified


> Host details page: components not reconfigured after deleting their host
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-22912
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22912
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.7.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>            Priority: Major
>             Fix For: 3.0.0, 2.7.0
>
>
> # When deleting a host, after components deletion config changes not triggered, as opposed to when they removed individually.
>  # When adding/deleting component config modification triggered before actual call to add/delete a component, so even if the call fails then configs would be modified



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)