yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

We can't backport the fix to pike because the cross-cell listing
framework is not in pike and would be a big backport.

https://review.openstack.org/#/q/topic:instance-
list+(status:open+OR+status:merged)

** Changed in: nova/pike
       Status: Confirmed => Won't Fix

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

Title:
  Nova should list instances even if it can't connect to a cell DB

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) pike series:
  Won't Fix
Status in OpenStack Compute (nova) queens series:
  In Progress

Bug description:
  Description
  ===========
  One of the goals of cells is to allow nova scale and to have cells as failure domains.
  However, if a cell DB goes down nova doesn't list any instance. Even if the project doesn't have any instance in the affected cell. This affects all users.

  The behavior that I would expect is nova to show what's available from
  the nova_api DB if a cell DB is not available. (UUIDs and can we look
  into the request_spec?)

  Steps to reproduce
  ==================
  Have at least 2 child cells.
  Stop the DB in one of them.

  "nova list" fails with "ERROR (ClientException): Unexpected API Error."
  Not given any more information to the user.

  Expected result
  ===============
  List the project instances.
  For the instances in the affect cell, list the available information in the nova_api.

  Actual result
  =============
  $nova list
  fails without showing the project instances.

  Environment
  ===========
  nova master (commit: 8d21d711000fff80eb367692b157d09b6532923f)

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