Description of problem: When user tries to add a new object with already taken name to the store, condor-configure-store first wants to edit attributes of the object and then it fails. Better is to first check the name if it's not taken and after that edit the object. That is how condor-configure-store behaves in previous version of condor-wallaby-tools. Version-Release number of selected component (if applicable): condor-wallaby-tools-5.0.3-2. How reproducible: 100% Steps to Reproduce: 1. e.g. create some feature # ccs -a -f Feat :wq Console Connection Established... Adding the following feature: Feat 2. try to add that feature again # ccs -a -f Feat :wq Console Connection Established... Adding the following feature: Feat Couldn't create feature Feat (Feature name Feat is already taken) fatal: AddFeature returned non-zero Actual results: The tool need set of object attributes even when the object name is already taken Expected results: The object creation is rejected before the editing of object Additional info:
Fixed upstream on: BZ880231-check-before-edit
Tested with: condor-wallaby-tools-5.0.5-1 Tested on: RHEL6 i386,x86_64 RHEL5 i386,x86_64 # ccs -a -f Feat Console Connection Established... Adding the following feature: Feat with {} Modifying the following feature: Feat with {:annotation=>""} # ccs -a -f Feat Console Connection Established... fatal: Feature(s) Feat already exist >>> verified