Skip to content
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

No refresh on connection lost #66

Closed
sandrobonazzola opened this issue May 25, 2015 · 7 comments

Comments

2 participants
@sandrobonazzola
Copy link
Member

commented May 25, 2015

Once you've connected moVirt app to the engine, if the connection goes down the app doesn't refresh the state keeping last state displayed.

For example you can see a VM still in start-up and the host up and running also if the engine has been disconnected 20 days before.

@sandrobonazzola

This comment has been minimized.

Copy link
Member Author

commented May 25, 2015

screenshot_2015-05-16-19-09-50
screenshot_2015-05-16-19-10-10
screenshot_2015-05-16-19-10-42

@jelkosz

This comment has been minimized.

Copy link
Member

commented May 25, 2015

@sandrobonazzola Hey Sandro! If you manually trigger the refresh (e.g. pull down) it starts working again or you need to restart the whole app?

@sandrobonazzola

This comment has been minimized.

Copy link
Member Author

commented May 25, 2015

manually triggering the refresh shows a rest request error. restarting the app or the phone doesn't update the state.

@jelkosz

This comment has been minimized.

Copy link
Member

commented May 26, 2015

@sandrobonazzola well, I can not simulate this so Im going to flood with with questions:

  • when you go to Settings->Connection Settings ->press Save Account it should enforce re-login. If you do this, it helps?
  • if not, are you sure the connection went back properly? e.g. if you try to access the same URL as configured in connection settings from mobile browser, can you access it?
  • what android version do you have? There are some issues with certificates on android 4.1 so maybe with reconnect as well. But I have not seen it...
@sandrobonazzola

This comment has been minimized.

Copy link
Member Author

commented May 26, 2015

Please note that the server is unreachable, not up anymore on the same ip address.
The issue is that even if the engine is not reachable it still report host up and vm booting.

save account give an I/O error since the engine is not there anymore.
after the failure, the host is still reported up and the vm booting.

Android 4.4.2 - Samsung S5 mini

@jelkosz

This comment has been minimized.

Copy link
Member

commented May 26, 2015

ah, I finally understand!
So the problem is not that moVirt does not reconnect after the engine is up again but that it does not notify you that he does not have a connection!
OK, will fix that, thank you!

@jelkosz jelkosz closed this Jun 26, 2015

@jelkosz

This comment has been minimized.

Copy link
Member

commented Jun 26, 2015

fixed by: #76

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.