Description of problem:
If re-run the installer to finish a failed install or to adjust configuration parameters, the storage node will not be available to the JBoss ON system.

WARN  [org.rhq.enterprise.server.storage.StorageClientManagerBean] (EJB default - 2) Storage client subsystem wasn't initialized. The RHQ server will be set to MAINTENANCE mode. Please verify  that the storage cluster is operational.: java.lang.RuntimeException: Authentication error on host jboss.example.com/192.168.1.1: Username and/or password are incorrect
	at org.rhq.enterprise.server.storage.StorageClientManagerBean.checkSchemaCompability(StorageClientManagerBean.java:257) [rhq-server.jar:4.9.0.JON320GA]
	at org.rhq.enterprise.server.storage.StorageClientManagerBean.createSession(StorageClientManagerBean.java:341) [rhq-server.jar:4.9.0.JON320GA]
	at org.rhq.enterprise.server.storage.StorageClientManagerBean.init(StorageClientManagerBean.java:154) [rhq-server.jar:4.9.0.JON320GA]
	at org.rhq.enterprise.server.storage.StorageClientManagerBean.storageSessionMaintenance(StorageClientManagerBean.java:129) [rhq-server.jar:4.9.0.JON320GA]
    ...
Caused by: com.datastax.driver.core.exceptions.AuthenticationException: Authentication error on host jboss.example.com/192.168.1.1: Username and/or password are incorrect
	at com.datastax.driver.core.Connection.initializeTransport(Connection.java:168) [cassandra-driver-core-1.0.2.jar:]
	at com.datastax.driver.core.Connection.<init>(Connection.java:129) [cassandra-driver-core-1.0.2.jar:]
    ...
	at org.rhq.cassandra.util.ClusterBuilder.build(ClusterBuilder.java:130) [rhq-cassandra-util-4.9.0.JON320GA.jar:4.9.0.JON320GA]
	at org.rhq.cassandra.schema.SessionManager.initSession(SessionManager.java:33) [rhq-cassandra-schema-4.9.0.JON320GA.jar:4.9.0.JON320GA]
	at org.rhq.cassandra.schema.AbstractManager.initClusterSession(AbstractManager.java:100) [rhq-cassandra-schema-4.9.0.JON320GA.jar:4.9.0.JON320GA]
	at org.rhq.cassandra.schema.AbstractManager.initClusterSession(AbstractManager.java:90) [rhq-cassandra-schema-4.9.0.JON320GA.jar:4.9.0.JON320GA]
	at org.rhq.cassandra.schema.VersionManager.checkCompatibility(VersionManager.java:257) [rhq-cassandra-schema-4.9.0.JON320GA.jar:4.9.0.JON320GA]
	at org.rhq.cassandra.schema.SchemaManager.checkCompatibility(SchemaManager.java:112) [rhq-cassandra-schema-4.9.0.JON320GA.jar:4.9.0.JON320GA]
	at org.rhq.enterprise.server.storage.StorageClientManagerBean.checkSchemaCompability(StorageClientManagerBean.java:253) [rhq-server.jar:4.9.0.JON320GA]
	... 49 more

Version-Release number of selected component (if applicable):
3.2.0

How reproducible:
Always

Steps to Reproduce:
1.  Create a shell script that can be used to simulate a storage node shutdown failure similar to what happens in bug 1089757:

        cat >/tmp/neverDie <<EOF
#/bin/sh

_okayToExit=false

function handleSignal() {
    echo "A signal was received. \$1"
    \${_okayToExit} && exit \$1
    _okayToExit=true
}

trap handleSignal SIGHUP SIGINT SIGTERM

while true; do
    echo "Running..."
    sleep 5s
done
EOF
        chmod +x /tmp/neverDie

2.  Run rhqctl install:

        "${RHQ_SERVER_HOME}"'/bin/rhqctl' install 
        
3.  After the installer has been running for a few seconds, execute the following commands from another terminal:

        /tmp/neverDie &
        newPID=$!
        echo -n ${newPID} >"${RHQ_SERVER_HOME}"'/rhq-storage/bin/cassandra.pid'

    You must ensure that RHQ_SERVER_HOME is set to the correct path. The goal here is to replace the Cassandra PID stored in cassandra.pid with the one of our neverDie shell script. This is to simulate a shutdown failure for the RHQ Storage Node during the execution of the installer.
    
4.  Wait for the installer to fail:

        11:08:30,024 ERROR [org.rhq.server.control.RHQControl] Process [11951] did not finish yet. Terminate it manually and retry.
        11:08:30,025 WARN  [org.rhq.server.control.command.Install] UNDO: Removing agent install directory
        11:08:30,047 WARN  [org.rhq.server.control.command.Install] UNDO: Removing server-installed marker file and management user
        11:08:30,048 WARN  [org.rhq.server.control.command.Install] UNDO: Stopping component: --server
        11:08:30,049 WARN  [org.rhq.server.control.command.Install] UNDO: Stopping component: --storage
        11:08:40,069 WARN  [org.rhq.server.control.command.Install] UNDO: Removing storage node data and install directories
        11:08:40,098 WARN  [org.rhq.server.control.command.Install] UNDO: Reverting server properties file

5.  Re-execute the installer using the --start command-line argument:

        "${RHQ_SERVER_HOME}"'/bin/rhqctl' install --start

Actual results:
Server logs the following warning and enters maintenance mode:

    WARN  [org.rhq.enterprise.server.storage.StorageClientManagerBean] (EJB default - 2) Storage client subsystem wasn't initialized. The RHQ server will be set to MAINTENANCE mode. Please verify  that the storage cluster is operational.: java.lang.RuntimeException: Authentication error on host jboss.example.com/192.168.1.1: Username and/or password are incorrect


Expected results:
Storage node and cluster is running just fine and no warnings or errors logged in server.log.

Additional info:
It is not clear why this happens. During testing, if I delete the contents of the file system, and re-run the installer, this problem doesn't seem to occur. Perhaps the rhq-server.properties and rhq-storage.properties files are not actually getting reverted back to their pre-install versions? Keep in mind that I would expect the user provided configuration to remain in the property files but not the stuff that was added/changed during the install itself.