ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gunnar Tapper (JIRA)" <>
Subject [jira] [Created] (AMBARI-1567) Ambari's behavior is confusing after ambari-server reset
Date Wed, 06 Mar 2013 20:52:14 GMT
Gunnar Tapper created AMBARI-1567:

             Summary: Ambari's behavior is confusing after ambari-server reset
                 Key: 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:

View raw message