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

Bug 1568377

Summary:	test_templates_negative.TemplateYAMLNegativeTestJSON attempts to connect to external service
Product:	Red Hat OpenStack	Reporter:	Attila Fazekas <afazekas>
Component:	openstack-tempest	Assignee:	Chandan Kumar <chkumar>
Status:	CLOSED ERRATA	QA Contact:	Martin Kopec <mkopec>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0 (Liberty)	CC:	apevec, chkumar, jschluet, lhh, slinaber, udesale, whayutin
Target Milestone:	zstream	Keywords:	Triaged, ZStream
Target Release:	8.0 (Liberty)	Flags:	mkopec: needinfo-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tempest-liberty-20160413.4.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1568839 (view as bug list)		Environment:
Last Closed:	2018-07-05 12:29:07 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:	1568839

Description Attila Fazekas 2018-04-17 11:31:01 UTC

The test_templates_negative haves heat to connect to an external service. www.example.com is a registered existing domain, and it also has an AAAA record.

But if you do not have external ipv6 connectivity the test fails after a long time.

Tempest should not depends on the example.org behavior.

Comment 9 Martin Kopec 2018-06-07 10:05:28 UTC

The issue was resolved in the new version of openstack-tempest-liberty package. Tested by an internal Jenkins jobs with director_puddle: 2018-06-05.1.

Comment 12 errata-xmlrpc 2018-07-05 12:29:07 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/RHBA-2018:2133