Hide Forgot
Description of problem: I was doing a deployment in a nested virt. environment, destroyed the fusor VM and restarted it. Once it was restarted I went back to the UI and in the deployments screen it said the deployment was in error, however if you clicked on the deployment it looked like it was in progress and had no issues. Clicking on the details tab showed that the main task was in error. The power was not recycled till it was past the sync portion of the deployment. Version-Release number of selected component (if applicable): QCI-1.1-RHEL-7-20170130.t.0 How reproducible: Only tried it once. Steps to Reproduce: 1. Start a deployment. 2. Reboot the fusor machine while the deployment is going. 3. Examine the deployments page, and the progress overview page and the progress overview details page. Actual results: The different pages will report results that are inconsistent with one another. Expected results: consistent reporting of the state of the deployment.
The issue as I understand it is.. WebUI has it's own state, it assumes that after it has retrieved data from the REST API that data will be valid. Problem here is that WebUI retrieved data, then the backend REST API was destroyed and recreated so it's at a fresh spot...no deployment running yet webui doesn't know that and displays like a task is still running. Could look into adding better error detection so when polling if the state has changed, tasks don't exist, etc the wizard flow detects this and notifies user.