Nova doesn't check service type before deleting compute service

Bug #1587702 reported by Fei Long Wang on 2016-06-01

This bug report will be marked for expiration in 36 days if no further activity occurs. (find out why)

8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Undecided
Unassigned

Bug Description

Now nova service delete is using the same logic for compute service and the others. See https://github.com/openstack/nova/blame/stable/kilo/nova/db/sqlalchemy/api.py#L446

And as a result, if there is any service running associated with compute service(on the same host), then when delete the service, the compute service will be deleted as well.

Fei Long Wang (flwang) on 2016-06-01
Changed in nova:
assignee: nobody → Fei Long Wang (flwang)

Fix proposed to branch: master
Review: https://review.openstack.org/323633

Changed in nova:
status: New → In Progress

Change abandoned by Fei Long Wang (<email address hidden>) on branch: master
Review: https://review.openstack.org/323633

Sean Dague (sdague) wrote :

Automatically discovered version kilo in description. If this is incorrect, please update the description to include 'nova version: ...'

tags: added: openstack-version.kilo
Sean Dague (sdague) wrote :

There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments.

Changed in nova:
status: In Progress → New
assignee: Fei Long Wang (flwang) → nobody
Sean Dague (sdague) wrote :

The link to where this was doesn't seem to work. Also is this still true on master after the work to make the service code handle computes differently?

Changed in nova:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers