Bug 1613751 - Change downstream Neutron Tempest plugin to be branchless
Summary: Change downstream Neutron Tempest plugin to be branchless
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-neutron-tests-tempest
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 15.0 (Stein)
Assignee: Bernard Cafarelli
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-08 09:42 UTC by Eran Kuris
Modified: 2019-09-26 10:45 UTC (History)
4 users (show)

Fixed In Version: python-neutron-tests-tempest-0.4.0-0.20190729040454.a7bb161.el8ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-21 11:16:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:2811 0 None None None 2019-09-21 11:18:35 UTC

Description Eran Kuris 2018-08-08 09:42:52 UTC
Description of problem:
need to backport neutron dns test  to osp13
https://review.openstack.org/#/c/571495/13

Version-Release number of selected component (if applicable):


How reproducible:

100%
Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Assaf Muller 2018-08-10 14:09:55 UTC
The upstream Neutron Tempest plugin is branchless, it should be the same in RDO and OSP. Currently RDO and OSP don't have a master branch, only a queens/OSP 13 branch, which is weird. It's being tagged in both 13 and 14 but the 13 version is outdated.

Comment 6 Bernard Cafarelli 2019-08-01 14:09:34 UTC
Upstream plugin is now tagged as "cycle-with-intermediary" release model, and RDO imports grabbed the newly released 0.4.0 in supported branches. So we can consider the goal achieved

Comment 15 errata-xmlrpc 2019-09-21 11:16:49 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:2811


Note You need to log in before you can comment on or make changes to this bug.