Description of problem: # rhc-admin-move -h == Synopsis rhc-admin-move: Move an app from one node to another == Usage rhc-admin-move OPTIONS Options: --gear_uuid <gear_uuid> Gear uuid to move, if app is a scalable application --app_uuid <app_uuid> Application uuid that the gear belongs to (Optional argument) --destination_district_uuid <district_uuid> Destination district uuid -i|--target_server_identity <server_identity> Target server identity -p|--node_profile <node_profile> Node profile -t|--timeout timeout --allow_change_district Allow the move to be between districts -h|--help Show Usage info --gear_uuid <gear_uuid> Gear uuid to move, if app is a scalable application Accutally even when moving a non-scalable app, still need specify this option, so "if app is a scalable application" should be removed. --app_uuid <app_uuid> Application uuid that the gear belongs to (Optional argument) This option looks like a little redundant. Becasue one gear only belong to one app, not possible to belong to multiple app. It should be removed now. Version-Release number of selected component (if applicable): devenv_1802 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Fixed with rev# 94989beac3f1796b5dc6479da8e0577a70ffad22
Verified this bug with devenv_1806, and PASS. # rhc-admin-move -h == Synopsis rhc-admin-move: Move an app from one node to another == Usage rhc-admin-move OPTIONS Options: --gear_uuid <gear_uuid> Gear uuid to move --destination_district_uuid <district_uuid> Destination district uuid -i|--target_server_identity <server_identity> Target server identity -p|--node_profile <node_profile> Node profile -t|--timeout timeout --allow_change_district Allow the move to be between districts -h|--help Show Usage info