Description of problem: If engine-setup tries to disconnect a remote dwhd by setting DisconnectDwh to 1, it does not set it back to 0 on failure. Next attempts to start dwhd will then fail (currently silently, see bug 1168141). Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. setup engine on macine A and dwh on machine B, start both 2. somehow prevent dwh access to engine db (e.g. firewall) 3. run engine-setup on A, it will try to stop dwh and fail 4. allow access of dwh to engine db (revert step 2) 5. try to restart dwh Actual results: dwh fails to start Expected results: success Additional info: step 2 is currently "happening" also due to bug 1167801 .
Workaround: manually set it to 0 by running on engine db: update vdc_options set option_value='0' where option_name = 'DisconnectDwh';