[Openstack] [Nova] Do nova evacuate / migrate, but it's failed.

Shinobu Kinjo shinobu.kj at gmail.com
Thu Mar 3 10:59:16 UTC 2016


Mmm... I don't see any incompatibility issue.

If there is any pointer regarding to unexpected behaviour of evacuate
/ migrate in Juno, it would be helpful.

Cheers,
S

On Mon, Feb 29, 2016 at 7:43 PM, Shinobu Kinjo <shinobu.kj at gmail.com> wrote:
> On Mon, Feb 29, 2016 at 5:49 PM, Merlin Blom <merlin.blom at nionex.net> wrote:
>>
>>
>> Am 29.02.2016 um 09:12 schrieb Shinobu Kinjo:
>>>
>>> Thanks for your reply.
>>>
>>> On Mon, Feb 29, 2016 at 4:58 PM, Merlin Blom <merlin.blom at nionex.net>
>>> wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> When I do "nova evacuate  ${instance} ${host}", evacuate process ends
>>>>> up with being failed.
>>>>
>>>>
>>>> Did you find any error messages in /var/log/nova/
>>>>
>>>> I had the problem too. In my case the CPUs of the Hosts are not
>>>> compatible.
>>>
>>> Which CPU did you use?
>>
>>
>> We used some old HP G5 and G7 for testing porpose.
>>>
>>> I've not checked /var/log/nova regarding to hardware.
>>> What did the log message say to you when you hit same issue?
>>
>> I think the nova-scheduler error was: CPU of Hosts not compatible
>
> This would be much help!
> I will have a look at logs and let me update you.
>
> BTW regarding to that message, it seems to be related to libvirt.
> Did you find out what actually caused this issue?
>
> Or @anyone??
>
> Cheers,
>
>>
>>
>>
>>>
>>> BTW I'm using intel x520 hba, xeon cpu which some with dell server. I
>>> believe ram should not cause this issue.
>>> Storage is a bit tricky, which is vnx -;
>>>
>>> Cheers,
>>>
>>>>> There is an information of that instance in nova.instances and
>>>>> "deleted_at" flag is set.
>>>>>
>>>>> "nova list" show nothing about that instance.
>>>>>
>>>>> But there is a still directory in /var/lib/nova/instances/${instance}
>>>>>
>>>>> And virsh list --all show me-;
>>>>>
>>>>> virsh list --all
>>>>>    Id    Name                           State
>>>>> ----------------------------------------------------
>>>>>    -     ${instance}              shut off
>>>>>
>>>>> Is there any bug related to above behaviour in Juno?
>>>>> If there is any pointer, that would be much appreciated.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list:
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>>> Post to     : openstack at lists.openstack.org
>>>>> Unsubscribe :
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list:
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>> Post to     : openstack at lists.openstack.org
>>>> Unsubscribe :
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>
>>>
>>>
>>
>>
>> _______________________________________________
>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to     : openstack at lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
>
> --
> Email:
> shinobu at linux.com
> GitHub:
> shinobu-x
> Blog:
> Life with Distributed Computational System based on OpenSource



-- 
Email:
shinobu at linux.com
GitHub:
shinobu-x
Blog:
Life with Distributed Computational System based on OpenSource




More information about the Openstack mailing list