Bug 1293101 - Cross Hosts test fails due to bad rebase.
Summary: Cross Hosts test fails due to bad rebase.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tempest
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ga
: 8.0 (Liberty)
Assignee: Daniel Mellado
QA Contact: tkammer
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-20 09:33 UTC by yfried
Modified: 2016-03-10 07:28 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-10 07:28:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 259746 0 None MERGED Security Groups multi-node scenario 2020-06-19 14:53:26 UTC
Red Hat Product Errata RHEA-2016:0603 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 8 Enhancement Advisory 2016-04-08 00:53:53 UTC

Description yfried 2015-12-20 09:33:09 UTC
Description of problem:
test_security_groups_cross_hosts module fails because upstream code has changed.
Need to fix downstream test and rebase.

Note: Pushed the test upstream. If/when merged, root cause will be removed. 


Traceback (most recent call last):
  File "/home/cloud-user/tempest-dir/tempest/test.py", line 127, in wrapper
    return f(self, *func_args, **func_kwargs)
  File "/home/cloud-user/tempest-dir/tempest/scenario/test_security_groups_basic_ops.py", line 495, in test_port_update_new_security_group
    server = self._create_server(name, new_tenant)
  File "/home/cloud-user/tempest-dir/tempest/scenario/test_security_groups_cross_hosts.py", line 56, in _create_server
    self.servers = self._distribute_servers()
  File "/home/cloud-user/tempest-dir/tempest/scenario/test_security_groups_cross_hosts.py", line 84, in _distribute_servers
    'VERIFY_RESIZE')
TypeError: wait_for_server_status() takes at least 3 arguments (2 given)


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