trove mistral client not instantiated correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-mistralclient |
Invalid
|
Undecided
|
Unassigned | ||
python-troveclient |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Trying to use trove CLI that in turn uses mistral doesn't work, it tries to connect to mistral over localhost and ignores the catalog.
I'm not sure if this is a bug in trove client or mistral client.
To fix this I needed to modify troveclient to instantiate the mistral client by adding the
service_
argument to mistral client.
Possibly the mistral client shouldn't need this to be passed in as it should be the default so maybe this bug is in mistral client?
troveclient==2.8.0
mistralclient=
File "/usr/lib/
sys.argv[1:]))
File "/usr/lib/
args.
File "/usr/lib/
schedules = cs.backups.
File "/usr/lib/
for cron_trig in mistral_
File "/usr/lib/
return self._list(
File "/usr/lib/
resp = self.http_
File "/usr/lib/
resp = func(self, *args, **kwargs)
File "/usr/lib/
return requests.
File "/usr/lib/
return request('get', url, params=params, **kwargs)
File "/usr/lib/
return session.
File "/usr/lib/
resp = self.send(prep, **send_kwargs)
File "/usr/lib/
r = adapter.
File "/usr/lib/
raise ConnectionError(e, request=request)
ConnectionError: HTTPConnectionP
Changed in python-mistralclient: | |
status: | New → Invalid |
Changed in python-troveclient: | |
status: | New → Fix Released |
Sorry I should've tried the latest clients to see if this is still broken. Looks like its fixed.
troveclient==2.12.0 =3.1.2
mistralclient=