3:37 p.m.
Currently running RDO/Havana deployed via Foreman on a multi-compute node stack
(Controller, Neutron, and three Nova-Compute servers)
When spawning an instance, it correctly spawns and reports/registers to the Foreman
dashboard.
The problem is that the hypervisor/compute-node that is hosting the instance will then
begin to report:
Level
Resource
message
err
Puppet
Could not prefetch firewall provider 'iptables': Invalid address from IPAddr.new:
FA:16:3E:67:64:A4
err
/Firewall[001 nova compute incoming]
Could not evaluate: Invalid address from IPAddr.new: FA:16:3E:67:64:A4
err
/Firewall[002 vxlan udp]
Could not evaluate: Invalid address from IPAddr.new: FA:16:3E:67:64:A4
When the instance is deleted, the error will disappear also.
Any assistance/insight would be appreciated.
Thank you.
6:08 p.m.
Hi,
I saw this issue too, I was just about to report it.
If I understand correctly, this is because of the openvswitch iptables
rules which are created (for security groups?)
`service iptables status`
...
Chain neutron-openvswi-s0ec3eb58-0 (1 references)
num target prot opt source destination
1 RETURN all -- 10.0.0.12 0.0.0.0/0 MAC
FA:16:3E:2E:B7:E3
2 DROP all -- 0.0.0.0/0 0.0.0.0/0
....
In your case, the MAC address is different -- FA:16:3E:67:64:A4
This issue also appears on icehouse w/ foreman, so it looks like it may be
the puppet modules at fault here
Andrew.
On Fri, Mar 28, 2014 at 7:37 AM, St. George, Allan L. <
ALLAN.L.ST.GEORGE(a)leidos.com> wrote:
Currently running RDO/Havana deployed via Foreman on a
multi-compute
node stack (Controller, Neutron, and three Nova-Compute servers)
When spawning an instance, it correctly spawns and reports/registers to
the Foreman dashboard.
The problem is that the hypervisor/compute-node that is hosting the
instance will then begin to report:
*Level*
*Resource*
*message*
*err*
Puppet
Could not prefetch firewall provider 'iptables': Invalid address from
IPAddr.new: FA:16:3E:67:64:A4
*err*
/Firewall[001 nova compute incoming]
Could not evaluate: Invalid address from IPAddr.new: FA:16:3E:67:64:A4
*err*
/Firewall[002 vxlan udp]
Could not evaluate: Invalid address from IPAddr.new: FA:16:3E:67:64:A4
When the instance is deleted, the error will disappear also.
Any assistance/insight would be appreciated.
Thank you.
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
5:08 a.m.
New subject: [Rdo-list] Multicast does not work with ML2/VxLAN
Hi,
I am trying ML2/VXLAN on RDO Havana 2013.2.2 on CentOS 6.5 in a 3-nodes setup. OVS version
is 1.11.0.
I enable multicast by setting vxlan_group = 239.1.1.1 in
/etc/neutron/plugins/ml2/ml2_conf.ini.
But from the tcpdump, I find the VM broadcast traffic still goes via multiple unicast
packages between OVS agent nodes.
How to make that multicast really work ?
My ml2_confi.ini:
[ml2]
type_drivers = vxlan
tenant_network_types = vxlan
mechanism_drivers = openvswitch
[ml2_type_flat]
[ml2_type_vlan]
[ml2_type_gre]
[ml2_type_vxlan]
vni_ranges = 1001:2000
vxlan_group = 239.1.1.1
[database]
sql_connection = mysql://neutron:83105f1d6ded47cc@10.142.0.101/neutron_ml2
[securitygroup]
firewall_driver = dummy_value_to_enable_security_groups_in_server
My ovs_neutron_plugin.ini on every OVS agent node:
[OVS]
vxlan_udp_port=4789
tunnel_type=vxlan
tunnel_id_ranges=1001:2000
tenant_network_type=vxlan
local_ip=10.142.255.101 #This varies on different node
enable_tunneling=True
[AGENT]
tunnel_types = vxlan
polling_interval=2
[SECURITYGROUP]
firewall_driver=neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
Kimi
3904
days inactive
3905
days old
2 comments
3 participants
participants (3)
-
Andrew Lau -
St. George, Allan L. -
Zhang, Kimi (NSN - FI/Espoo)