When the host is down does not necessarily compute service is down.
Bug #1443851 reported by
Ratnaker
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ruby OpenStack Compute API Binding |
New
|
Undecided
|
Ratnaker |
Bug Description
During evacuate operation, api checking if the compute service is down. But it is not always the case. There may be instances where compute service is still up when the host is down. for ex: If the compute service is running on a different system rather than on the host itself.
affects: | openstack-manuals → ruby-openstack-compute |
Changed in ruby-openstack-compute: | |
assignee: | nobody → Ratnaker (ratnaker-katipally) |
To post a comment you must log in.
The code
if self.servicegro up_api. service_ is_up(service) :
LOG. error(_ LE('Instance compute service state on %s '
'expected to be down, but it was up.'), inst_host) ComputeServiceI nUse(host= inst_host)
raise exception.
Can be changed to
if self.servicegro up_api. service_ is_up(service) :
LOG. error(_ LE('Instance compute service state on %s '
'expected to be down, but it was up.'), inst_host) ComputeServiceI nUse(host= inst_host)
raise exception. ComputeServiceI nUse(host= inst_host)
#raise exception.
if host.state is not 'power_off' or 'crashed' or 'error':