EC2 API noauth user_id is invalid

Bug #831995 reported by Dan Prince
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
High
Vish Ishaya

Bug Description

I'm getting Smokestack failures w/ revision 1478 of nova using the new noauth manager. The issue seems to stem from the fact that the OSAPI and EC2 API's noauth code now generates and use different user_id's within the same project.

After creating a keypair I found the following in my key_pairs table:

mysql> select user_id from key_pairs;
+----------------------+
| user_id |
+----------------------+
| hdJbmeRuyJAkRtWc9c6t |
+----------------------+

---

The OSAPI noauth manager however still uses 'admin' as the user_id in the RequestContext. So using the same novarc file:

-You can create a keypair with the EC2 API.
-But you can no longer use that keypair via the OSAPI (because your user_id is different)

Related branches

Dan Prince (dan-prince)
Changed in nova:
importance: Undecided → High
Revision history for this message
Vish Ishaya (vishvananda) wrote :

Thanks, dan. The issue is that NoAuth doesn't have any way to look up a user_id from an access key, so the novarc file is wrong. I will come up with a workaround for this.

Changed in nova:
assignee: nobody → Vish Ishaya (vishvananda)
milestone: none → diablo-4
Changed in nova:
status: New → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: diablo-4 → 2011.3
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.