| Summary: | tempest.api.orchestration.stacks.test_neutron_resources.NeutronResourcesTestJSON failing due wrong heat_metadata and heat_waitcondition_server address | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Arx Cruz <acruz> | |
| Component: | rhosp-director | Assignee: | Angus Thomas <athomas> | |
| Status: | CLOSED DUPLICATE | QA Contact: | Martin Kopec <mkopec> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 8.0 (Liberty) | CC: | afazekas, augol, david.costakos, dbecker, jcoufal, mburns, mcornea, mmagr, morazi, psedlak, rhel-osp-director-maint, shardy, tkammer, tvignaud, zbitter | |
| Target Milestone: | --- | Keywords: | Automation, AutomationBlocker | |
| Target Release: | 12.0 (Pike) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1570052 (view as bug list) | Environment: | ||
| Last Closed: | 2017-07-17 13:41:38 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: | ||
| Bug Depends On: | ||||
| Bug Blocks: | 1570052 | |||
|
Description
Arx Cruz
2016-03-09 11:13:19 UTC
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10. In our case, it fails in IPv6 deployments (as the tenant network and vm used in test, has IPv4, and cannot reach IPv6 address). Though, unlike mentioned in bug 1425189 linked commits, the url's in heat.conf are set: > #heat_metadata_server_url = <None> > heat_metadata_server_url = http://[2620:52:0:13b8:5054:ff:fe3e:9]:8000 > #heat_waitcondition_server_url = <None> > heat_waitcondition_server_url = http://[2620:52:0:13b8:5054:ff:fe3e:9]:8000/v1/waitcondition > #heat_watch_server_url = So in our case it's different bug then this (in testcase, or our possibly setup/...). And this one could be solved by that bug 1425189 (at least for 11). Though unlike upstream reviews linked from bug 1425189, in our case the url are set (and so not defaulting to values from keystone catalog), which may be other issue. *** This bug has been marked as a duplicate of bug 1452677 *** |