New instance imagecache doesn't work with keystone: get_admin_context() doesn't set a valid token/strategy
Bug #934464 reported by
Vladimir Popovski
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Michael Still |
Bug Description
Admin context generated by context.
Without these fields properly set different "internal" nova tasks (like periodic_tasks) are unable to access image_service when Keystone is used.
As a result, new imagecache functionality added to Essex fails with ERROR:
401 Unauthorized
This server could not verify that you are authorized to access the document you requested. Either you supplied the wrong credentials (e.g., bad password), or your browser does not understand how to supply the credentials required.
Authentication required
Changed in nova: | |
status: | New → Confirmed |
assignee: | nobody → Michael Still (mikalstill) |
milestone: | none → essex-4 |
Changed in nova: | |
importance: | Undecided → Medium |
tags: | added: canonistack |
Changed in nova: | |
status: | Confirmed → In Progress |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-rc1 → 2012.1 |
To post a comment you must log in.
The context here comes from rom nova/service.py where Service. periodic_ tasks() just calls context. get_admin_ context( ), so I think the imagecache code is just the lucky first victim. It seems like the right fix is to make sure that admin contexts work correctly with keystone in general.