eted?
>
>
>
> Check the hypervisors that each server Nova knows about - I suspect at
> least one is expected to exist on the XenServer for which the compute will
> not start.
>
>
>
> Bob
>
>
>
> *From:* Adhi Priharmanto [mailto:adhi@gmail.com]
> *Sent:
: openstack ; #OpenStack External Email
Subject: Re: [Openstack] [Ocata-Xenserver] Nova-compute wouldn't start
Hi bob,
Thanks for your suggest, because it's non production use, I decide to hardcoded
clean up instance record from nova table, and finally nova-compute service was
running aga
compute will
> not start.
>
>
>
> Bob
>
>
>
> *From:* Adhi Priharmanto [mailto:adhi@gmail.com]
> *Sent:* 18 May 2017 16:40
> *To:* Bob Ball
> *Cc:* openstack ; #OpenStack External
> Email
> *Subject:* Re: [Openstack] [Ocata-Xenserver] Nova-compute wouldn&#x
compute will not start.
Bob
From: Adhi Priharmanto [mailto:adhi@gmail.com]
Sent: 18 May 2017 16:40
To: Bob Ball
Cc: openstack ; #OpenStack External Email
Subject: Re: [Openstack] [Ocata-Xenserver] Nova-compute wouldn't start
hi Bob,
I don't have any vm/instance on that compute/xense
hi Bob,
I don't have any vm/instance on that compute/xenserver , I'm deleted all vm
since last week.
On Thu, May 18, 2017 at 6:03 PM, Bob Ball wrote:
> Hi Adhi,
>
>
>
> Very interesting. I suspect that self._get_vif_ref, below, is returning
> None. This appears to be when the VM does not exi
Hi Adhi,
Very interesting. I suspect that self._get_vif_ref, below, is returning None.
This appears to be when the VM does not exist on the host - perhaps the VM was
renamed, deleted, or it has been migrated to a different host and Nova’s
records didn’t get updated?
I believe the issue is m
