On 2014-12-09 16:50:48 +0100 (+0100), Jakub Ruzicka wrote:
On 22.9.2014 17:24, Ihar Hrachyshka wrote:
[...]
Aren't clients supposed to be backwards compatible? Isn't it the exact
reason why we don't maintain stable branches for client modules?
Supposed, yes. However, it's not
Horizon's tests were recently broken by a change in the Ceilometer
client that removed a deprecated exception. The exception was deprecated
for a while already, but as it often is, nobody did the
work of removing all references to it from Horizon before it was too
late. Sure, in theory we should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 22/09/14 17:07, Radomir Dopieralski wrote:
Horizon's tests were recently broken by a change in the Ceilometer
client that removed a deprecated exception. The exception was
deprecated for a while already, but as it often is, nobody did the
On 09/22/2014 11:24 AM, Ihar Hrachyshka wrote:
On 22/09/14 17:07, Radomir Dopieralski wrote:
Horizon's tests were recently broken by a change in the Ceilometer
client that removed a deprecated exception. The exception was
deprecated for a while already, but as it often is, nobody did the
Regarding ceilometer client, we horizon team at least was not aware of
its deprecation.
It is not easy thta Horizon team is aware of such changes/warnings in
all integrated projects.
We might need some liaison from the integrated projects as other projects do.
Regarding client backward
The larger problem here is that this breaks running Horizon unit tests on
all existing installs of Horizon including Havana, Icehouse and Juno if
those installations update to the newest python-ceilometerclient. I'm not
sure how to handle that type of deprecation other than forcing all existing
On Sep 22, 2014, at 11:07 AM, Radomir Dopieralski openst...@sheep.art.pl
wrote:
Horizon's tests were recently broken by a change in the Ceilometer
client that removed a deprecated exception. The exception was deprecated
for a while already, but as it often is, nobody did the
work of
