New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes for Live Migrate UI #8521
Fixes for Live Migrate UI #8521
Conversation
@miq-bot add_label darga/yes |
@h-kataria please review |
@mansam got an error when i pressed Migrate selected Instance button for a Amazon Instance from a list view:
Also an error when tried to Migrate from Openstack Instance summary screen or list view
|
@mansam another error when i press submit button on Migrate screen after checking a checkbox "Block migration"
|
@h-kataria I have a set of fixes for a number of things with Live Migrate coming soon. |
* Move Live Migrate button to the openstack-specific single-vm bar * Gracefully flash an error if Live Migrate is selected from the list view for an instance that doesn't support it.
b34496a
to
b87f7ef
Compare
@h-kataria The committed updates should fix the problem you were experiencing as well as a few others I became aware of. |
@mansam when i try to migrate an instance, i see following error in log & and i get redirected back to previous screen list/details screen with a flash message "Unable to live migrate Instance "BradTest2": No route to host - connect(2) for 10.3.57.7:5000 (Errno::EHOSTUNREACH)": |
@h-kataria Hmm. That sounds like something is wrong with your openstack networking. "no route to host - connect(2) for 10.3.57.7:5000" -- it seems like it's trying to make a keystone API call to 10.3.57.7 and it can't reach it. Can manageiq reach both infra and cloud provider endpoints? |
@sseago i don't have an environment set up to connect to host, but in case it can't reach the host, it should still not show errors in log, it should only show a flash message in UI. |
@h-kataria My code is just catching the exception and parsing out the error into that message flash. The logging isn't coming from the UI code. |
Is it showing the error in log and the flash message now? I would have thought that this sort of thing would go to the logs as well as the UI, but presumably only at an 'info' level (or maybe 'debug')? |
@h-kataria Can you check whether the network call to |
@mansam getting 500 Internal Server Error on live_migrate_form_fields transaction |
Okay, that's why you see it in the logs even though the migrate call catches it. Needs exception handling for getting the host list when there's a networking failure like that. |
(that said, your migrate call is still going to fail due to whatever that networking issue is) |
@h-kataria it should now handle that exception case more gracefully when loading the list of hosts. |
👍 |
Checked commits mansam/manageiq@43d639c~...41e6610 with ruby 2.2.3, rubocop 0.37.2, and haml-lint 0.16.1 app/controllers/vm_cloud_controller.rb
app/views/vm_common/_live_migrate.html.haml
|
This fixes the UI issues I hit earlier. Works for me now. |
…at-dont-support-live-migrate Fixes for Live Migrate UI (cherry picked from commit ad14e24)
Update: Working on the Evacuate pull request with @sseago revealed a number of problems that applied to Live Migrate that this pull request is intended to resolve.
list view for an instance that doesn't support it.