User and database name inputs validated in MySQL model
Bug #1498573 reported by
Matthew Van Dijk
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
High
|
Matthew Van Dijk |
Bug Description
When inputting user and database names the values are validated against the MySQL models, regardless of the datastore, in the api layer. This can allow bad names and block valid names. Bad names which get by only get caught and throw exceptions at a later stage. An example is for MongoDB instance create with an invalid user name. The API layer allows it, but then during prepare the guest will hit an exception and go into ERROR, with the only information available to the user being in the taskmanager logs.
Changed in trove: | |
assignee: | nobody → Sonali Goyal (sonaligoyal654321) |
Changed in trove: | |
assignee: | Sonali Goyal (sonaligoyal654321) → Matthew Van Dijk (mvandijk) |
Changed in trove: | |
status: | New → In Progress |
Changed in trove: | |
importance: | Undecided → High |
Changed in trove: | |
milestone: | none → next |
Changed in trove: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
This is not a blocking issue, just UX.