Unable to create instance when multiple networks found

[Mark Kirkwood]

Ubuntu version 14.04 on x84_64.

This has been noted (and fixed) upstream:

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

I am running into this - in fact anyone will run into this if they configure neutron. Is an update from the latest icehouse branch planned?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Mark Kirkwood (mark-kirkwood)]

Further examination shows that the issue appears to be confined to the trove client package (python-troveclient) only. The server packages have been updated and have the nic parameter in their various object and method definitions, however the client code has not been updated to match.

I confirmed this by overwriting the contents of /usr/lib/python2.7/dist-packages/troveclient with the newer code and I could create an instance when multiple networks were visible to the tenant by specifying a nic.

[Mark Kirkwood (mark-kirkwood)]

Ping...

This looks to be pretty straightforward to solve - the client api set should really match the servers one. You guys have been so proactive with updating to the current *server* capabilities - but it is sad that this is essentially let down by having the older client that is completely unaware of the new capabilities.

While this is a very simple update for for me to do myself - the *whole point* of using a packaged solution is to avoid the nonsense of me doing packaging when you guys are much better at it...so I'd really like to see an update soon here please :-)

[James Page (james-page)]

Hi Mark

We can certainly get this resolved - do you know which version is required? The test-requirements.txt at release was still referring to a master generated tarball:

http://tarballs.openstack.org/python-troveclient/python-troveclient-master.tar.gz#egg=python-troveclient

[Mark Kirkwood (mark-kirkwood)]

It looks like they are not tagging or branching the python-troveclient code sufficiently, e.g:

$ cd python-trove
$ git branch -a
* master
  remotes/origin/HEAD -> origin/master
  remotes/origin/master

I merely patched the package with the latest client, which is what you guys should probably do - as the current situation (having the client api not matching the servers) makes trove essentially unusable.

[Mark Kirkwood (mark-kirkwood)]

I see that they have releases here https://github.com/openstack/python-troveclient/releases , I'll take a look at them and see which one(s) have the api to match the trove server package we have in Trusty.

[Mark Kirkwood (mark-kirkwood)]

Looks like /python-troveclient-1.0.4 is where the relevant changes occur.

[Rolf Leggewie (r0lf)]

utopic has seen the end of its life and is no longer receiving any updates. Marking the utopic task for this ticket as "Won't Fix".

[Corey Bryant (corey.bryant)]

This is fixed as of Kilo. Marking as Fix released for releases greater than Trusty/Icehouse.