Created attachment 592860 [details] cluster configuration Description of problem: "wallaby cluster-delete" allow to delete HA schedd configuration from wallaby store and not from cluster configuration when user doesn't input proper password. Version-Release number of selected component (if applicable): condor-7.6.5-0.15.el6 condor-classads-7.6.5-0.15.el6 condor-cluster-resource-agent-7.6.5-0.15.el6 condor-wallaby-base-db-1.22-4.el6 condor-wallaby-client-4.1.2-1.el6 condor-wallaby-tools-4.1.2-1.el6 python-condorutils-1.5-4.el6 python-qpid-0.14-8.el6 python-qpid-qmf-0.14-7.el6_2 python-wallabyclient-4.1.2-1.el6 qpid-cpp-client-0.14-16.el6 qpid-cpp-server-0.14-16.el6 qpid-qmf-0.14-7.el6_2 ruby-qpid-qmf-0.14-7.el6_2 ruby-wallaby-0.12.5-1.el6 wallaby-0.12.5-1.el6 wallaby-utils-0.12.5-1.el6 How reproducible: 100% Steps to Reproduce: 1. install and setup Condor pool and clustering 2. setup HA scheduler 3. rm -rf ~/.ccs 4. wallaby -H _wallaby_node_ cluster-delete name="_name_of_ha_schedd_" 5. don't type password, just hit enter 6. there is defined HA schedd in cluster but there is no HA schedd in wallaby store(Condor configuration) Expected results: "wallaby cluster-delete" should not allow to delete HA schedd configuration from wallaby store when user doesn't input proper ricci password.
Created attachment 592861 [details] wallaby configuration
If I use: cluster-remove-node cluster-add-node cluster-add-queryserver cluster-add-jobserver cluster-sync-to-store wallaby connects to store and change configuration without connecting to ricci. For example this means that add/remove node adds/removes node from store but it is still in cluster.conf. Packages: condor-7.6.5-0.16.el6.x86_64 condor-aviary-7.6.5-0.16.el6.x86_64 condor-classads-7.6.5-0.16.el6.x86_64 condor-cluster-resource-agent-7.6.5-0.16.el6.x86_64 condor-qmf-7.6.5-0.16.el6.x86_64 condor-wallaby-base-db-1.22-5.el6.noarch condor-wallaby-client-4.1.2-1.el6.noarch condor-wallaby-tools-4.1.2-1.el6.noarch python-condorutils-1.5-4.el6.noarch python-qpid-0.14-8.el6.noarch python-qpid-qmf-0.14-7.el6_2.x86_64 python-wallabyclient-4.1.2-1.el6.noarch qpid-cpp-client-0.14-16.el6.x86_64 qpid-cpp-server-0.14-16.el6.x86_64 qpid-qmf-0.14-7.el6_2.x86_64 qpid-tools-0.14-2.el6_2.noarch ruby-qpid-qmf-0.14-7.el6_2.x86_64 ruby-wallaby-0.12.5-10.el6.noarch wallaby-0.12.5-10.el6.noarch wallaby-utils-0.12.5-10.el6.noarch
*** Bug 838581 has been marked as a duplicate of this bug. ***
The wallaby-* commands will not to anything if they can't communicate with ccs. Additionally, they will error out on all important ccs commands as well. Updated branch: boysenberry-BZ833308-cluster-delete-stops-on-ccs-error
Tested on RHEL 6.3 x i386/x86_64 with condor-7.6.5-0.18 build and it works. -->VERIFIED