[Bug 1748280] Re: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower

[melanie witt]

On the surface, it seems like this is something we could check for in
the libvirt driver and skip the soft reboot timeout cycle if ARM64. The
question I have is, which architecture fields does "ARM64" map to in
nova? ARMV6 or ARMV7 or ARMV7B or AARCH64 or all of them? Or one that I
missed? [1]

[1]
https://github.com/openstack/nova/blob/da1669/nova/objects/fields.py#L108-L112

** Changed in: nova
   Importance: Undecided => Medium

** Changed in: nova
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1748280

Title:
  'nova reboot' on arm64 is just 'nova reboot --hard' but slower

Status in OpenStack Compute (nova):
  Confirmed
Status in nova package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Within Canonical's multi-architecture compute cloud, I observed that
  arm64 instances were taking an unreasonable amount of time to return
  from a 'nova reboot' (2 minutes +, vs. ~16s for POWER in the same
  cloud region).

  Digging into this, I find that a nova soft reboot request is doing
  nothing at all on arm64 (no events visible within the qemu guest, and
  no reboot is triggered within the guest), and then after some sort of
  timeout (~2m), 'nova reboot' falls back to a hard reset of the guest.

  Since this is entirely predictable on the arm64 platform (because
  there's no implementation of ACPI plumbed through), 'nova reboot' on
  arm64 should just skip straight to the hard reboot and save everyone
  some clock time.

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