Bug 1336433
Summary: | Openstack installation fails due to invalid firewall driver parameter | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Alexander Stafeyev <astafeye> |
Component: | openstack-packstack | Assignee: | Ivan Chavero <ichavero> |
Status: | CLOSED ERRATA | QA Contact: | Mike Burns <mburns> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 9.0 (Mitaka) | CC: | aortega, apevec, astafeye, ichavero, jschluet, mburns, nlevinki, sgordon, srevivo, tshefi |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | 10.0 (Newton) | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | openstack-packstack-9.0.0-0.20160922140727.3f43120.1.el7ost | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-12-14 15:33:39 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: |
Description
Alexander Stafeyev
2016-05-16 13:03:34 UTC
Hello, i haven't been able to reproduce your problem. Can you give me access to the system? You are correct. I managed to deploy when CONFIG_NEUTRON_L3_EXT_BRIDGE=br-ex and not "provider" Is "CONFIG_NEUTRON_L3_EXT_BRIDGE=provider the firewall puppet module does not accept this value." is a know issue? We did not encounter it in previous versions. Regarding the original issue- may be it can be reproduced on the same puddle. If on latest puddle , after fixing the "provider" value for "CONFIG_NEUTRON_L3_EXT_BRIDGE" the original issue will not be reproduced, we will need to decide if we want to try to chase it. BR I'm checking what's the best option are we waiting on anything other than the mentioned patch? we already have the package for this bug: openstack-packstack-9.0.0-0.20160922140727.3f43120.1.el7ost 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/RHEA-2016-2948.html |