Request context is not set correctly
Bug #1406539 reported by
yuanying
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Fix Released
|
High
|
yuanying |
Bug Description
In service/pod/bay controller, request context is not set correctly.
So authenticate information is not set in context.
This causes a problem in conductor, context object does not make sense.
Changed in magnum: | |
assignee: | nobody → yuanying (ootsuka) |
Changed in magnum: | |
status: | New → In Progress |
Changed in magnum: | |
importance: | Undecided → High |
Changed in magnum: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/144077 /git.openstack. org/cgit/ stackforge/ magnum/ commit/ ?id=c6c606b2779 513ac4bb80c7ab0 3b8994447b4f80
Committed: https:/
Submitter: Jenkins
Branch: master
commit c6c606b2779513a c4bb80c7ab03b89 94447b4f80
Author: OTSUKA, Yuanying <email address hidden>
Date: Fri Dec 26 13:50:40 2014 +0900
Split up extracting auth.py file
The auth.py file does a couple of things, It contains keystone authentication
and to set request context. So this split up to two files.
After this commit, request hook should be included in hooks.py.
Related-Bug: #1406539 e48f6fd4ca23911 717f918f9bb
Change-Id: I1754da40383976