Bug 1401798 - All LBaaS tests fails when running with latest version of tempest
Summary: All LBaaS tests fails when running with latest version of tempest
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron-lbaas
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z2
: 10.0 (Newton)
Assignee: Nir Magnezi
QA Contact: GenadiC
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-06 06:38 UTC by Toni Freger
Modified: 2019-09-10 14:09 UTC (History)
7 users (show)

Fixed In Version: openstack-neutron-lbaas-9.1.0-4.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-23 16:34:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1649083 0 None None None 2016-12-11 14:43:05 UTC
OpenStack gerrit 406033 0 None None None 2017-02-02 13:08:53 UTC
Red Hat Product Errata RHBA-2017:0314 0 normal SHIPPED_LIVE openstack-neutron bug fix advisory 2017-02-23 21:33:22 UTC

Description Toni Freger 2016-12-06 06:38:45 UTC 
Description of problem:
Tests successfully passed when running with tempest 13 version, for example when we run it with tox.

It fails in upstream as self.tenant_id parameter is missing if we running with latest version 


How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 8 GenadiC 2017-02-15 15:36:09 UTC 
neutron-lbaas tests run with the tempest master
https://rhos-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/RHOS/view/RHOS10/job/qe-DFG-neutron-10_director-rhel-7.3-virthost-3cont_2comp-ipv4-vxlan-lvm-lbaas-dvr/lastCompletedBuild/testReport/

Verified in openstack-neutron-ml2-9.2.0-2.el7ost.noarch
Comment 10 errata-xmlrpc 2017-02-23 16:34:10 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://rhn.redhat.com/errata/RHBA-2017-0314.html
Note You need to log in before you can comment on or make changes to this bug.