Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1644198

Summary:	DHCPAgentOVSTestCase tests fail on RHEL 7.6
Product:	Red Hat OpenStack	Reporter:	Arie Bregman <abregman>
Component:	openstack-neutron	Assignee:	Rodolfo Alonso <ralonsoh>
Status:	CLOSED EOL	QA Contact:	Roee Agiman <ragiman>
Severity:	high	Docs Contact:
Priority:	high
Version:	12.0 (Pike)	CC:	amuller, bhaley, chrisw, nyechiel, ralonsoh, skaplons
Target Milestone:	---	Keywords:	AutomationBlocker, Triaged, ZStream
Target Release:	12.0 (Pike)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-11.0.4-7.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1648301 1648999 (view as bug list)		Environment:
Last Closed:	2018-12-14 11:27:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1648301, 1648999

Description Arie Bregman 2018-10-30 08:27:20 UTC

Description of problem:

The following tests fail:

neutron.tests.functional.agent.test_dhcp_agent.DHCPAgentOVSTestCase.test_metadata_proxy_respawned
neutron.tests.functional.agent.test_dhcp_agent/DHCPAgentOVSTestCase/test_good_address_allocation
neutron.tests.functional.agent.test_dhcp_agent.DHCPAgentOVSTestCase.test_create_subnet_with_non64_ipv6_cidrs

Traceback:

Stderr: Option --wait-interval requires option --wait\n',)] is not false : prefix size of 0 triggered resync

and

RuntimeError: Metadata proxy didn't spawn


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


How reproducible: 100%


Steps to Reproduce:
1. Clone neutron
2. Checkout OSP 12 branch
3. Run dsvm-functional tests

Comment 3 Rodolfo Alonso 2018-10-31 17:09:10 UTC

Those three test cases are failing because "iptables-restore" is being called with the following command line:
  $ iptables-restore -w 0 -W 20000

--wait (-w) parameter cannot be zero. In case this parameter is zero, the following error will be returned:
  Option --wait-interval requires option --wait

Example:
  [root@dev02 iptables]# iptables-restore -w 1 -W 20000 ipt 

  [root@dev02 iptables]# iptables-restore -w 0 -W 20000 ipt 
  Option --wait-interval requires option --wait

The following bug was filled in launchpad: https://bugs.launchpad.net/neutron/+bug/1800884