After enabling authN, creating a second network for 'default' tenant fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Critical
|
dan wendlandt | ||
quantum (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
After enabling authN in quantum.conf, the authentication is working perfectly - verified with some test cmds.
Steps to reproduce:
a. enable authN in quantum.conf
b. restart quantum service
c. feed the OS env variables and get token $ keystone token-get
d. create a network -> $ quantum -t <token-id> create_net default net2
On the terminal screen, the error you get is:
An unexpected exception occured:unsupported operand type(s) for +: 'int' and 'str' (<type 'exceptions.
On the quantum screen session, the traceback is:
http://
However, the value is reflected in the db.
Please note:
a. Without AuthN enabled, we dont get the traceback
b. I get the traceback only when the 2nd network is created for the 'default' tenant, creating more networks work fine
I have tested it twice with a new devstack install.
Changed in quantum: | |
milestone: | none → essex-rc2 |
Changed in quantum: | |
milestone: | essex-rc2 → 2012.1 |
Changed in quantum (Ubuntu): | |
status: | New → Fix Released |
Hi Deepak,
it seems this failure is peculiar to the OVS plugin. It would be interesting if you can provide some more context in order to understand why it happens only when authentication is enabled.
As far as I recall, the authentication token is consumed in the API layer, and not forwarded to the plugin.