"Ignoring EndpointNotFound: The service catalog is empty" error when init_host

Bug #1408865 reported by wanghao on 2015-01-09
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Undecided
Unassigned

Bug Description

the scenario:

1. create a vm using bootable volume.

2. delete this vm

3. restart service nova-compute when vm's task state is deleting.

When nova-compute is up, vm became deleted successful, but the bootable volume is still in-use state and can't delete it using cinder delete volume.

The error point is when nova-compute is up, "init_host" will go to delete the vm whose task state is "deleting", but the context using is got from "nova.context.get_admin_context()" function. There is no auth_token. When call "self.volume_api.terminate_connection(context, bdm.volume_id, connector)" in deleting vm process, it will log "Ignoring EndpointNotFound: The service catalog is empty" warning and can't detach the bootable volume. The volume's status is still 'in-use' in cinder side.

wanghao (wanghao749) on 2015-01-09
Changed in nova:
assignee: nobody → wanghao (wanghao749)
Joe Gordon (jogo) on 2015-01-10
Changed in nova:
status: New → Confirmed
importance: Undecided → Low

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

Changed in nova:
status: Confirmed → In Progress
wanghao (wanghao749) on 2015-03-02
description: updated
zhangjialong (zhangjl) wrote :

Maybe ,we need a function or method to get 'real' context which contain project_id,user_id, service_catalog, then we can handle
the volume when init_host and execute the periodic_task named _run_pending_deletes

wanghao (wanghao749) wrote :

@zhangjl: Yes, in my first fix patch, I want to use cinder admin credentials to get real context.

tags: added: volumes
Changed in nova:
status: In Progress → Triaged
assignee: wanghao (wanghao749) → nobody

Change abandoned by John Garbutt (<email address hidden>) on branch: master
Review: https://review.openstack.org/147042
Reason: This patch seems to have stalled, lets abandon it.
Please restore the patch if that is no longer true.

Any questions, please catch me via email or on IRC johnthetubaguy

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY

Changed in nova:
importance: Low → Undecided
status: Triaged → Expired

Change abandoned by Michael Still (<email address hidden>) on branch: master
Review: https://review.openstack.org/296890
Reason: This code hasn't been updated in a long time, and is in merge conflict. I am going to abandon this review, but feel free to restore it if you're still working on this.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers