← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1738248] [NEW] "MSI-X is not supported by interrupt controller" when launching aarch64 instance on pike

 

Public bug reported:

Attempting to launch an aarch64 nova-compute-kvm instance on pike fails
with the error: "MSI-X is not supported by interrupt controller".

Longer form of the error: http://paste.ubuntu.com/26184308/

To reproduce, deploy openstack using the openstack-base bundle with juju
(https://jujucharms.com/openstack-base/).  This deploys on ubuntu xenial
using pike packages.

Then, configure tenants/users/networks/images in openstack, including
uploading a xenial cloud image to glance.

Then, try to start an instance.

Expected result is that the instance starts without errors, but the
actual result is that it fails with the error above.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: cdo-qa-blocker

** Attachment added: "sosreport-aurorus-20171214174356.tar.xz"
   https://bugs.launchpad.net/bugs/1738248/+attachment/5022720/+files/sosreport-aurorus-20171214174356.tar.xz

-- 
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/1738248

Title:
  "MSI-X is not supported by interrupt controller" when launching
  aarch64 instance on pike

Status in OpenStack Compute (nova):
  New

Bug description:
  Attempting to launch an aarch64 nova-compute-kvm instance on pike
  fails with the error: "MSI-X is not supported by interrupt
  controller".

  Longer form of the error: http://paste.ubuntu.com/26184308/

  To reproduce, deploy openstack using the openstack-base bundle with
  juju (https://jujucharms.com/openstack-base/).  This deploys on ubuntu
  xenial using pike packages.

  Then, configure tenants/users/networks/images in openstack, including
  uploading a xenial cloud image to glance.

  Then, try to start an instance.

  Expected result is that the instance starts without errors, but the
  actual result is that it fails with the error above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1738248/+subscriptions