trove client create call with optional user and database(s) args does not grant user access

[Dan Nguyen]

When you supply the optional command line args for user and databases during instance create the trove api does not grant the user privileges to the database.

$ trove --debug create dntest4 1001 --users dntest:dnpass --databases my database

+----------+--------------------------------------+
| Property | Value |
+----------+--------------------------------------+
| flavor | 1001 |
| id | 18961e76-8042-44d0-812f-74173ca7fedd |
| name | dntest4 |
| status | ACTIVE |
+----------+--------------------------------------+

$ trove database-list 18961e76-8042-44d0-812f-74173ca7fedd
+------------+
| name |
+------------+
| mydatabase |
+------------+

$ trove user-list 18961e76-8042-44d0-812f-74173ca7fedd
+--------+------+-----------+
| name | host | databases |
+--------+------+-----------+
| dntest | % | [] |
+--------+------+-----------+

mysql shows that there is only usage privileges for the new user.

Grants for dntest@%
GRANT USAGE ON *.* TO 'dntest'@'%' IDENTIFIED BY PASSWORD '*ED4215FA147DEDF8507B0C28E7AC8F6CFABBE881'

* To correct this you can use the user-grant-access api call.

$ trove user-grant-access 18961e76-8042-44d0-812f-74173ca7fedd detest mydatabase

$ trove user-list 18961e76-8042-44d0-812f-74173ca7fedd
+--------+------+----------------------------+
| name | host | databases |
+--------+------+----------------------------+
| dntest | % | [{u'name': u'mydatabase'}] |
+--------+------+----------------------------+

The proposed fix would be to make this additional call through the trove client.

[Dan Nguyen (daniel-a-nguyen)]

After looking at the code I'm considering making the this fix in the trove api itself.

[Dan Nguyen (daniel-a-nguyen)]

We have work arounds so we'll keep this bug in the background for now.

[Dan Nguyen (daniel-a-nguyen)]

A fix for this requires a bit more discussion. It would probably involve client and server side changes.
The bit that might need to be figured out is how we would want to form the POST body from the python-troveclient to associate users to databases.

It could get messy if say you have more that one user specified and more than one database and only wanted some users to use database 'a' and others to only use database 'b'.

It might be worth considering removing the --user --database(s) optional args from the python trove client.

[Sushil Kumar (sushil-kumar2)]

I think this got resoved with another new one reported

https://bugs.launchpad.net/trove/+bug/1272421

[Sushil Kumar (sushil-kumar2)]

Resolved using https://review.openstack.org/#/c/68983/

[Sushil Kumar (sushil-kumar2)]

Updating it as fix committed as problem does not stands any more and got fixed through another bug reported(with duplication missed).