neutron-rally job failing for stable/pike and stable/ocata

Bug #1777506 reported by Slawek Kaplonski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Critical
Slawek Kaplonski
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (stable/pike)

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/576451

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (stable/ocata)

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/576567

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/pike)

Reviewed: https://review.openstack.org/576451
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a4233220d8e897bba262ce8e5700994213583ccb
Submitter: Zuul
Branch: stable/pike

commit a4233220d8e897bba262ce8e5700994213583ccb
Author: Slawek Kaplonski <email address hidden>
Date: Tue Jun 19 11:25:34 2018 +0200

    Use rally 0.12.1 release for stable/pike branch.

    Rally does not have any alignment of own tags to OpenStack releases.
    In theory it should be possible to launch the latest Rally against
    old clouds.

    To follow the common processes and policy, Rally synchronized own
    dependencies (python-*client's and oslo.* libs) with g-r. It made a
    conflict between installed versions by stable/pike@devstack and rally
    itself.
    With Rally master branch it became an error (Rally's team is
    working on moving in-tree OpenStack plugins to the separate repository
    openstack/rally-openstack).
    Rally 0.12.1 is the latest release which doesn't contain a breaking
    change.

    Ideally, to avoid such issues in future, Rally devstack plugin and
    zuul job should install Rally in a virtual environment, but such
    change requires more time for investigation and implementation.

    So this patch is a quick workaround to avoid version conflict
    of python dependencies.

    Change-Id: I73ef5c978e66a89bb70be28468e0d1f40a71d94f
    Closes-Bug: #1777506

tags: added: in-stable-pike
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/ocata)

Reviewed: https://review.openstack.org/576567
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1afa908c7fa0d593bd5b4092caf6ed6cda17c0b0
Submitter: Zuul
Branch: stable/ocata

commit 1afa908c7fa0d593bd5b4092caf6ed6cda17c0b0
Author: Slawek Kaplonski <email address hidden>
Date: Tue Jun 19 11:25:34 2018 +0200

    Use rally 0.12.1 release for stable/ocata branch

    Rally does not have any alignment of own tags to OpenStack releases.
    In theory it should be possible to launch the latest Rally against
    old clouds.

    To follow the common processes and policy, Rally synchronized own
    dependencies (python-*client's and oslo.* libs) with g-r. It made a
    conflict between installed versions by stable/pike@devstack and rally
    itself.
    With Rally master branch it became an error (Rally's team is
    working on moving in-tree OpenStack plugins to the separate repository
    openstack/rally-openstack).
    Rally 0.12.1 is the latest release which doesn't contain a breaking
    change.

    Ideally, to avoid such issues in future, Rally devstack plugin and
    zuul job should install Rally in a virtual environment, but such
    change requires more time for investigation and implementation.

    So this patch is a quick workaround to avoid version conflict
    of python dependencies.

    Change-Id: I73ef5c978e66a89bb70be28468e0d1f40a71d94f
    Closes-Bug: #1777506

tags: added: in-stable-ocata
Changed in neutron:
status: Confirmed → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 11.0.6

This issue was fixed in the openstack/neutron 11.0.6 release.

Changed in neutron:
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron ocata-eol

This issue was fixed in the openstack/neutron ocata-eol release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.