yahoo-eng-team team mailing list archive

[javeme <javaloveme@xxxxxxxxx>]

Public bug reported:

raise ComputeServiceNotExist instead of ComputeServiceUnavailable if
host is not found.

When performing a live migration, I passed a wrong host parameter, and then I got a wrong result like this:
"Compute service of host-1 is unavailable at this time".
I thought the compute service stopped, but the fact was I passed a host id instead of a host name, therefore it could not find the host.

In order to distinguish the error "host not found" from the error
"service not available", I think we should raise a different exception
like ComputeServiceNotExist.

** Affects: nova
     Importance: Undecided
     Assignee: javeme (javaloveme)
         Status: In Progress

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

Title:
  raise ComputeServiceNotExist instead of ComputeServiceUnavailable if
  host is not found

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  raise ComputeServiceNotExist instead of ComputeServiceUnavailable if
  host is not found.

  When performing a live migration, I passed a wrong host parameter, and then I got a wrong result like this:
  "Compute service of host-1 is unavailable at this time".
  I thought the compute service stopped, but the fact was I passed a host id instead of a host name, therefore it could not find the host.

  In order to distinguish the error "host not found" from the error
  "service not available", I think we should raise a different exception
  like ComputeServiceNotExist.

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