ec2tokens errors in v2 api after Ocata upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
High
|
Jose Castro Leon | ||
Ocata |
Fix Committed
|
High
|
Unassigned |
Bug Description
After the ocata upgrade we are seeing some errors while authenticating users using v2 api and ec2 credentials
Same as reported in here:
https:/
2017-05-11 16:05:22.453 6081 INFO keystone.
2017-05-11 16:05:22.721 6081 ERROR keystone.
2017-05-11 16:05:22.721 6081 ERROR keystone.
2017-05-11 16:05:22.721 6081 ERROR keystone.
2017-05-11 16:05:22.721 6081 ERROR keystone.
2017-05-11 16:05:22.721 6081 ERROR keystone.
2017-05-11 16:05:22.721 6081 ERROR keystone.
2017-05-11 16:05:22.721 6081 ERROR keystone.
2017-05-11 16:05:22.721 6081 ERROR keystone.
2017-05-11 16:05:22.721 6081 ERROR keystone.
2017-05-11 16:05:22.721 6081 ERROR keystone.
The commit "Remove metadata from token provider" with ID (I4b37289c06df2
Also the removal of the issue_v2_token token provider method did not have effect in the ec2 v2 controller that it is still using it.
The bug was introduced in Ocata and it is still there in the master branch
Changed in keystone: | |
milestone: | none → pike-3 |
tags: | added: office-hours |
Changed in keystone: | |
milestone: | pike-3 → pike-rc1 |
Fix proposed to branch: master /review. openstack. org/465530
Review: https:/