Bug 1142500
| Summary: | Rubygem-Staypuft: HA Neutron+GRE deployment - puppet agent exits with error on controllers: Error 400 on SERVER: Local ip for ovs agent must be set when tunneling is enabled at /etc/puppet/environments/production/modules/neutron/manifests/agents/ovs.pp:32 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Alexander Chuzhoy <sasha> | ||||
| Component: | rubygem-staypuft | Assignee: | Imre Farkas <ifarkas> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Asaf Hirshberg <ahirshbe> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 5.0 (RHEL 7) | CC: | adahms, ajeain, athomas, ddomingo, dsneddon, mburns, sclewis, yeylon | ||||
| Target Milestone: | z2 | Keywords: | ZStream | ||||
| Target Release: | Installer | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| URL: | https://trello.com/c/xah3Fy17/232-validation-around-network-assignment-i-e-public-api-must-be-on-network-with-ipam-enabled | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Known Issue | |||||
| Doc Text: |
When you create a deployment that uses Neutron networking and VXLAN or GRE for tenant networks, the user interface for the Red Hat Enterprise Linux OpenStack Platform installer does not validate whether the subnet carrying the Tenant network traffic type provides an IP address. This results in the following error when attempting to provision the deployment:
Error 400 on SERVER: Local ip for ovs agent must be set when tunneling is enabled at /etc/puppet/environments/production/modules/neutron/manifests/agents/ovs.pp:32
As a workaround, you can ensure the subnet carrying the Tenant network traffic type can access an external DHCP service or is assigned a static IP address by the installer.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-11-04 17:02:37 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: | |||||||
| Attachments: |
|
||||||
|
Description
Alexander Chuzhoy
2014-09-16 21:56:53 UTC
Created attachment 938247 [details]
messages from controllers + foreman.log from the staypuft
Spoke directly with Lars on this. The summary is that the tenant network requires an IP address when using VXLAN or GRE for Neutron Networking. Adding Known Issue text and removing blocker flag. The work for this in Staypuft is to add validations as specified in the doc text Mike and/or Lars: this part is unclear to me in terms of validations "Ensure that the Tenant subnet either has an external DHCP server or will get a static IP address assigned from Foreman" Foreman UI validations won't detect presence of an external dhcp server, so what exactly should validations be confirming? Shouldn't it just be a matter of the subnet config must be set to dhcp mode or ipam = internal and static? this may go away with the subnet form re-design Ahh, so basically the intention is to prevent the user from choosing "ipam=none" and "static" boot mode? I imagine this would apply to *all* network traffic types -- i.e. if static boot, then IPAM must be enabled? pretty sure it only applies with gre and vxlan (based on what i wrote in the tech note) (In reply to Mike Burns from comment #9) > pretty sure it only applies with gre and vxlan (based on what i wrote in the > tech note) That's correct. GRE and VXLAN need an IP address in order to have an endpoint for the tunnel. Tunnels will be established between hypervisors and between each hypervisor and the Neutron networker. With VLAN mode a tagged VLAN is attached to the VIF, so an IP address is not required on the interface where the tenant VLANs are trunked. I think this will end up as a testonly bug once the refactored subnet UI makes it in, as the new subnet UI should prevent the invalid choices from being selected. This bug should be resolved by the "Improve Foreman Subnets form for Staypuft specific use-cases" dev task The "Improve Foreman Subnets form for Staypuft specific use-cases" PR is merged: https://github.com/theforeman/staypuft/commit/0458470858ace7de5befd3a9a5daba45b0d1e52e Environment: rhel-osp-installer-0.4.5-2.el6ost.noarch (poodle) puppet-3.6.2-2.el7.noarch rhel 6.6 I deployed the same setup, HA-neutron(GRE) and I didnt encountered those erros. the puppet have finished running and the nics with that configured with the tenant role was populated with ip addresses. 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/RHBA-2014-1800.html |