Hide Forgot
Description of problem: after selecting the host for a vm migration i can no longer pick a different host Version-Release number of selected component (if applicable): running on 5.6.2.0 How reproducible: Steps to Reproduce: 1. create a vpshere 55 provider ( i used the non nested one of cfme-qa) 2. provision a vm (i used a damn small linux one) 1. start the submission of a vm migration request 2. select a host 3. click a different host Actual results: after the wait period the original host stays selected Expected results: the new host should be selected Additional info:
https://10.16.5.156/miq_request/prov_field_changed/environment__placement_ds_name=4&id=new Failed to load resource: net::ERR_CONNECTION_REFUSED is a repeat error displayed at the end of the wait period
Ronny, I am unable to recreate this issue locally on upstream and 5.6 codebase, can you please provide further details such as logs, it will be good if you have an appliance that i can access to be able to see this issue. Thanks, ~Harpreet
Hi Harpreet, i could not replicate the issue on normal operation myself, however i could trigger it by suspending the appliance vm. as soon as the vm was suspended the ux went "nonsense" without showing errors to the users an error message telling the user something "appliance not answering, please check your connection", perhaps worded in more detail, should be a big help cheers, Ronny
Ronny, I am still unable to recreate this issue locally, can i access your appliance to be able to recreate it there and troubleshoot the issue. Additionally can you upload logs so i can gather some additional information from those. Thanks, ~Harpreet
can we coordinate this in order to demonstrate the issue i will need to *suspend* the appliance while the form for the migration request is being filled with data thanks, Ronny
Laura, Can you work with Ronny and see if you can recreate this issue. Thanks, ~Harpreet
demonstration and verification happened in coordination with lgalis via irc
The title/description needs to be modified to reflect the actual issue - while on the migration page - if the connection to the appliance is lost, the ui does not display an error message.
New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/6a17bf42f0a9064541bd863c5f2e96195a4794f2 commit 6a17bf42f0a9064541bd863c5f2e96195a4794f2 Author: Martin Hradil <himdel> AuthorDate: Mon Nov 28 13:32:51 2016 -0500 Commit: Oleg Barenboim <chessbyte> CommitDate: Mon Nov 28 13:47:27 2016 -0500 Merge pull request #12785 from lgalis/display_error_when_ajax_request_fails Add flash message for miqJqueryRequest errors (cherry picked from commit 27f0f82189b830886390ce3132048ee220f5e391) https://bugzilla.redhat.com/show_bug.cgi?id=1378481 app/assets/javascripts/miq_application.js | 16 ++++++++++++++-- spec/javascripts/miq_application_spec.js | 27 +++++++++++++++++++++++++++ 2 files changed, 41 insertions(+), 2 deletions(-)
verified on 5.8.0.14-rc3