Openstack nova live migration pain

hai wu haiwu.us at gmail.com
Fri Sep 10 19:50:08 UTC 2021


>From controller, this command is saying 4.0.0:

$ openstack --version
openstack 4.0.0

Is this one what you are looking for? Currently using Debian native
openstack deb packages for this train release.

On Fri, Sep 10, 2021 at 2:39 PM Thomas Goirand <zigo at debian.org> wrote:
>
> On 9/10/21 5:53 PM, hai wu wrote:
> > This is Openstack train release. Nova live migration is extremely
> > painful to deal with. Everytime we complete a live migration,
> > nova-compute service on the source host would still be up and
> > runnning, but it would always fail to further increment the
> > report_count database field in nova database, host heartbeat purpose,
> > thus controller would think the hypervisor host failed via its is_up()
> > function checking on report_count and updated_at fields iirc. So we
> > end up having to manually migrate one vm at a time, then restart
> > service, then manually migrate the next vm ..
> >
> > Any ideas? I already tried setting debug=True for nova.conf even for
> > database tracing, but thus far I could not find any obvious error
> > message. Each time the live migration (no shared storage) would
> > succeed, but each time we will have to restart nova-compute service.
> > This is so bad ..
> >
> > Any suggestions on this would be highly appreciated.
> >
> > Thanks,
> > Hai
>
> Hi,
>
> I experienced the same kind of trouble with Nova as well, but this seems
> to be fixed in the more recent versions. What is the exact point release
> that you're running?
>
> Cheers,
>
> Thomas Goirand (zigo)
>



More information about the openstack-discuss mailing list