Description of problem: Some names configuration entries have changed, see https://bugzilla.redhat.com/show_bug.cgi?id=681648 so they should be changed also in configuration database. Version-Release number of selected component (if applicable): condor-wallaby-base-db-1.14-1 How reproducible: 100% Actual results: There are old names of conf. entries of low latency in conf. database. Expected results: There will be new names of conf. entries of low latency in conf. database.
Pushed upstream on branch: BZ724907-carod-param-names
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: C: The subsystem used by low-latency in MRG Grid's configuration changed from LOW-LATENCY to CAROD C:The configuration in the base-db used by remote configuration still used the old subsystem F: Updated the base-db to use the new subsystem. R: Configuring low-latency with remote configuration will create configurations with the new subsystem.
Tested with RHEL 5.8/6.1 x x86_64/i386 with condor-wallaby-base-db-1.16-2 and configuration entries are renamed OK. -> VERIFIED
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,4 +1,2 @@ -C: The subsystem used by low-latency in MRG Grid's configuration changed from LOW-LATENCY to CAROD +The subsystem used by low-latency scheduling in MRG Grid's configuration changed from LOW-LATENCY to CAROD but the configuration in the base-db used by remote configuration still used the old subsystem. Now, the base-db -C:The configuration in the base-db used by remote configuration still used the old subsystem +has been updated to use the new subsystem and low-latency scheduling with remote configuration creates configurations with the new subsystem.-F: Updated the base-db to use the new subsystem. -R: Configuring low-latency with remote configuration will create configurations with the new subsystem.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-0045.html