© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Quoting Graham Hayes (grahamhayes): "Not all project IDs are UUIDs unfortunately - in the past I have worked on clouds were they were ints, The keystone validator is very loose [1]
...
1 - https:/
"[2]
So we can't just add validation into Neutron for tenant_id to be UUID - this is incorrect, won't be accepted by upstream and more importantly may break existing customers deployments.
The proper way would be to validate all tenant IDs with keystone like was done in nova [3] and currently is being replicated in designate [4].
If we are to replicate this in Neutron then the validation code should be refactored to a common library (oslo) and be used from all projects where needed. This is an upstream master feature which will take significant time to land.
Even if implemented, these patches will be hardly backportable to Mitaka (which is 5-6 releases back).
Given above - closing as won't fix.
A recommendation would be to maybe fix this in ODL V1 driver by handling/skipping a non-UUID exception which should be fairly simple and backportable unless I'm too naive.
[2] https:/
[3] https:/
[4] https:/