[openstack-dev] [Heat] [Ceilometer] [depfreeze] bug is unresolved due to requirements freeze

Ihar Hrachyshka ihrachys at redhat.com
Thu Apr 2 12:36:00 UTC 2015

Hash: SHA1

On 04/02/2015 01:58 PM, Eoghan Glynn wrote:
>> Pavlo Shchelokovskyy wrote:
>>> unfortunately, in Heat we do not have yet integration tests for
>>> all the Heat resources (creating them in real OpenStack), and
>>> Ceilometer alarms are in those not covered. In unit tests the
>>> real client is of course mocked out. When we stumbled on this
>>> issue during normal Heat usage, we promptly raised a bug
>>> suggesting to make a new release, but propagating it to
>>> requirements took some time. The gate is not affected as it 
>>> installs as per >= in requirements the latest which is 1.0.13.
>>> With 1.0.12 ceilometerclient and Heat-Kilo, the Ceilometer
>>> alarm resource not "doesn't work quite as expected", it can not
>>> be created at all, failing any stack that has it in the
>>> template.
>> I'm +1 on the change.
>> Let's wait until tomorrow to make sure this is not completely 
>> unacceptable to packagers.

Packaging wise, it does not seem like a great deal, since all
new/updated dependencies that were touched from 1.0.12 to 1.0.13 are
already present in other Kilo components for a long time (all of them
are covered by neutron kilo deps). The package hasn't changed a lot
(just a new CONTRIBUTE file was introduced that can be easily
added/skipped from downstream packages).

Though, have we actually determined that the issue we try to tackle is
still present in Kilo? I don't see an update to the latest email from
Pavlo in the thread where he said that he cannot reproduce it.

So in the end, if it fixes a valid bug, I don't see a huge problem
packaging wise to bump the version. Though there can be other
concerns, like exposing a new code to users that could potentially get
new bugs with the bump. [I personally don't consider it a huge risk

Version: GnuPG v1


More information about the OpenStack-dev mailing list