Activity log for bug #1538837

Date Who What changed Old value New value Message
2016-01-28 03:16:55 javeme bug added bug
2016-01-28 03:23:35 OpenStack Infra nova: status New In Progress
2016-01-28 03:23:35 OpenStack Infra nova: assignee javeme (javaloveme)
2016-02-12 08:41:23 Pawel Koniszewski nova: importance Undecided Low
2016-02-12 08:41:33 Pawel Koniszewski tags live-migration
2016-02-15 11:51:10 Pawel Koniszewski summary raise ComputeServiceNotExist instead of ComputeServiceUnavailable if host is not found Invalid exception raised (ComputeServiceUnavailable) if host is not found
2016-02-15 11:51:21 Pawel Koniszewski 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. Invalid exception raised (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.
2016-07-26 13:17:40 OpenStack Infra nova: status In Progress Fix Released