ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-1567) Ambari's behavior is confusing after ambari-server reset
Date Sun, 10 Mar 2013 21:25:12 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598388#comment-13598388
] 

Mahadev konar commented on AMBARI-1567:
---------------------------------------

Gunnar for the configuration directories, did you delete them manually? 
                
> Ambari's behavior is confusing after ambari-server reset
> --------------------------------------------------------
>
>                 Key: AMBARI-1567
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1567
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.2.1
>         Environment: RHEL 6.2. Ambari 1.2.1.
>            Reporter: Gunnar Tapper
>
> After using ambari-server reset, the Ambari client allows you to redefine the cluster.

> However, reset doesn't remove previous configuration files causing Ambari to warn you
about the existence of configuration and other directories. In addition, a button is provided
to rerun the pre check, causing you to think that the configuration directories should be
removed.
> If you remove the configuration directories, then Ambari starts complaining that the
directories don't exists (they are likely still registered in the puppet database or something).
As a result, it's no longer possible to install the cluster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message