[Yahoo-eng-team] [Bug 1535918] Re: instance.host not updated on evacuation

nova (2:13.1.4-0ubuntu4.1~cloud0) trusty-mitaka; urgency=medium . * New update for the Ubuntu Cloud Archive. . nova (2:13.1.4-0ubuntu4.1) xenial; urgency=medium . * d/nova.conf: Add connection strings to default config for sqlite. This enables daemons to start by default and fixes

[Yahoo-eng-team] [Bug 1535918] Re: instance.host not updated on evacuation

This bug was fixed in the package nova - 2:13.1.4-0ubuntu3 --- nova (2:13.1.4-0ubuntu3) xenial; urgency=medium * Fix evacuation error when nova-compute is down just after VM is started. - d/p/make-sure-to-rebuild-claim-on-recreate.patch (backported from newton

[Yahoo-eng-team] [Bug 1535918] Re: instance.host not updated on evacuation

** Also affects: cloud-archive/mitaka Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1535918 Title: instance.host not

[Yahoo-eng-team] [Bug 1535918] Re: instance.host not updated on evacuation

** Also affects: nova (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: nova (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: nova (Ubuntu Artful) Status: New => Fix Released ** Changed in: nova (Ubuntu Zesty) Status: New => Fix

[Yahoo-eng-team] [Bug 1535918] Re: instance.host not updated on evacuation

** Also affects: nova (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: nova (Ubuntu Xenial) Assignee: (unassigned) => Seyeong Kim (xtrusia) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack

[Yahoo-eng-team] [Bug 1535918] Re: instance.host not updated on evacuation

** Changed in: cloud-archive Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1535918 Title: instance.host not updated on evacuation

[Yahoo-eng-team] [Bug 1535918] Re: instance.host not updated on evacuation

** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: nova (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] - Affected to Xenial, UCA Mitaka + Affected to Xenial Mitaka, UCA Mitaka just after creating vm and

[Yahoo-eng-team] [Bug 1535918] Re: instance.host not updated on evacuation

Reviewed: https://review.openstack.org/371048 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a5b920a197c70d2ae08a1e1335d979857f923b4f Submitter: Jenkins Branch:master commit a5b920a197c70d2ae08a1e1335d979857f923b4f Author: Artom Lifshitz Date:

[Yahoo-eng-team] [Bug 1535918] Re: instance.host not updated on evacuation

I am able to reproduce this same issue on a multinode devstack running libvirt. On the source host, the last call to nova/network/base_api.py::update_instance_cache_with_nw_info for a specific instance before the source host crashes has the nw_info passed in as a VIF object with the "active"

[Yahoo-eng-team] [Bug 1535918] Re: instance.host not updated on evacuation

The issue with the PowerVM driver is actually in neutron. I set up a libvirt environment, and the difference is that the PowerVM VIF is for some reason in a BUILD state, where as it is ACTIVE in libvirt. If the PowerVM VIF was in an ACTIVE state, this wouldn't occur, and no neutron events would