
It's running on my vm01 host and when I tried to manually migrate it on another host (vm03) which had a "ghost" VM count (it's a fresh cluster install with just the HE running in it), the migration started, the VMs count in vm03 went to 0 but then the HE machine got stuck in migration. Actually it's still perfectly running on vm01, it seems that it's just a database state. Is there a way to force a refresh? -- Davide Ferrari Senior Systems Engineer

Following this https://access.redhat.com/discussions/688043 even if it's 4 years old, I've resatrted ovirt-engine on HE vm and now the status is OK again 2016-09-26 11:24 GMT+02:00 Davide Ferrari <davide@billymob.com>:
It's running on my vm01 host and when I tried to manually migrate it on another host (vm03) which had a "ghost" VM count (it's a fresh cluster install with just the HE running in it), the migration started, the VMs count in vm03 went to 0 but then the HE machine got stuck in migration.
Actually it's still perfectly running on vm01, it seems that it's just a database state. Is there a way to force a refresh?
-- Davide Ferrari Senior Systems Engineer
-- Davide Ferrari Senior Systems Engineer

I'm pretty sure we fixed that already, what version are you runing? On 26 September 2016 at 12:39, Davide Ferrari <davide@billymob.com> wrote:
Following this
https://access.redhat.com/discussions/688043
even if it's 4 years old, I've resatrted ovirt-engine on HE vm and now the status is OK again
2016-09-26 11:24 GMT+02:00 Davide Ferrari <davide@billymob.com>:
It's running on my vm01 host and when I tried to manually migrate it on another host (vm03) which had a "ghost" VM count (it's a fresh cluster install with just the HE running in it), the migration started, the VMs count in vm03 went to 0 but then the HE machine got stuck in migration.
Actually it's still perfectly running on vm01, it seems that it's just a database state. Is there a way to force a refresh?
-- Davide Ferrari Senior Systems Engineer
-- Davide Ferrari Senior Systems Engineer
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

4.0.3-1.el7.centos 2016-09-26 14:07 GMT+02:00 Roy Golan <rgolan@redhat.com>:
I'm pretty sure we fixed that already, what version are you runing?
On 26 September 2016 at 12:39, Davide Ferrari <davide@billymob.com> wrote:
Following this
https://access.redhat.com/discussions/688043
even if it's 4 years old, I've resatrted ovirt-engine on HE vm and now the status is OK again
2016-09-26 11:24 GMT+02:00 Davide Ferrari <davide@billymob.com>:
It's running on my vm01 host and when I tried to manually migrate it on another host (vm03) which had a "ghost" VM count (it's a fresh cluster install with just the HE running in it), the migration started, the VMs count in vm03 went to 0 but then the HE machine got stuck in migration.
Actually it's still perfectly running on vm01, it seems that it's just a database state. Is there a way to force a refresh?
-- Davide Ferrari Senior Systems Engineer
-- Davide Ferrari Senior Systems Engineer
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Davide Ferrari Senior Systems Engineer

please open a bug and put the engine.log as well as vdsm.log from vm01 and vm03 On 26 September 2016 at 18:23, Davide Ferrari <davide@billymob.com> wrote:
4.0.3-1.el7.centos
2016-09-26 14:07 GMT+02:00 Roy Golan <rgolan@redhat.com>:
I'm pretty sure we fixed that already, what version are you runing?
On 26 September 2016 at 12:39, Davide Ferrari <davide@billymob.com> wrote:
Following this
https://access.redhat.com/discussions/688043
even if it's 4 years old, I've resatrted ovirt-engine on HE vm and now the status is OK again
2016-09-26 11:24 GMT+02:00 Davide Ferrari <davide@billymob.com>:
It's running on my vm01 host and when I tried to manually migrate it on another host (vm03) which had a "ghost" VM count (it's a fresh cluster install with just the HE running in it), the migration started, the VMs count in vm03 went to 0 but then the HE machine got stuck in migration.
Actually it's still perfectly running on vm01, it seems that it's just a database state. Is there a way to force a refresh?
-- Davide Ferrari Senior Systems Engineer
-- Davide Ferrari Senior Systems Engineer
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Davide Ferrari Senior Systems Engineer
participants (2)
-
Davide Ferrari
-
Roy Golan