Inconsistent behavior parsing sql_connection between glance-registry.conf vs nova.conf

Bug #1043662 reported by Joe Julian
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glance
Invalid
Medium
Unassigned

Bug Description

Version 2012.1.1

With a valid mysql password, "1bM+7uQe6" (for example), in nova.conf I, not surprisingly, have to url encode it, "1bM%2b7uQe6" and it works fine.

In glance-registry.conf it errors because ConfigParser is trying to expand the % symbol.

The expected behavior is that they would both work the same way and just accept the url encoded password.

Revision history for this message
Jay Pipes (jaypipes) wrote :

Strange that this is showing different behaviour, as both Glance and Nova should be using the same upstream openstack-common cfg code. Thanks for the report, we'll look into it. Might be as simple as updating the openstack-common code in Glance.

Changed in glance:
importance: Undecided → Medium
Revision history for this message
Jay Pipes (jaypipes) wrote :

Joe, can you check to see if trunk also experiences this behaviour? Thanks!

Revision history for this message
Joe Julian (joe.julian) wrote :

Of course, I should have tried that first. Thanks.

Changed in glance:
status: New → Invalid
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.