[openstack-dev] [ironic] state of the stable/mitaka branches

Dmitry Tantsur dtantsur at redhat.com
Thu Mar 2 10:39:24 UTC 2017


On 03/01/2017 08:19 PM, Jay Faulkner wrote:
>
>> On Mar 1, 2017, at 11:15 AM, Pavlo Shchelokovskyy <pshchelokovskyy at mirantis.com> wrote:
>>
>> Greetings ironicers,
>>
>> I'd like to discuss the state of the gates in ironic and other related projects for stable/mitaka branch.
>>
>> Today while making some test patches to old branches I discovered the following problems:
>>
>> python-ironicclient/stable/mitaka
>> All unit-test-like jobs are broken due to not handling upper constraints. Because of it a newer than actually supported python-openstackclient is installed, which already lacks some modules python-ironicclient tries to import (these were moved to osc-lib).
>> I've proposed a patch that copies current way of dealing with upper constraints in tox envs [0], gates are passing.
>>
>> ironic/stable/mitaka
>> While not actually being gated on, using virtualbmc+ipmitool drivers is broken. The reason is again related to upper constraints as what happens is old enough version of pyghmi (from mitaka upper constraints) is installed with most recent virtualbmc (not in upper constraints), and those versions are incompatible.
>> This highlights a question whether we should propose virtualbmc to upper constraints too to avoid such problems in the future.
>> Meanwhile a quick fix would be to hard-code the supported virtualbmc version in the ironic's devstack plugin for mitaka release.
>> Although not strictly supported for Mitaka release, I'd like that functionality to be working on stable/mitaka gates to test for upcoming removal of *_ssh drivers.
>>
>> I did not test other projects yet.
>>
>
> I can attest jobs are broken for stable/mitaka on ironic-lib as well — our jobs build docs unconditionally, and ironic-lib had no docs in Mitaka.

Oh, fun.

Well, the docs job is easy to exclude. But we seem to have virtualbmc-based jobs 
there. As I already wrote in another message, I'm not even sure they're supposed 
to work..

>
> -
> Jay Faulkner
> OSIC
>
>> With all the above, the question is should we really fix the gates for the mitaka branch now? According to OpenStack release page [1] the Mitaka release will reach end-of-life on April 10, 2017.
>>
>> [0] https://review.openstack.org/#/c/439742/
>> [1] https://releases.openstack.org/#release-series
>>
>> Cheers,
>> Dr. Pavlo Shchelokovskyy
>> Senior Software Engineer
>> Mirantis Inc
>> www.mirantis.com
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>




More information about the OpenStack-dev mailing list