Hide Forgot
Description of problem: Setup.. two nodes.. Everything on $controller_ip except for the compute node which is on $compute_public_ip Using the following packstack config.. packstack --gen-answer-file=/root/packstack_config.txt sed \ -e 's|_HOST=.*|_HOST=$controller_public_ip|' \ -e 's|_HOSTS=.*|_HOSTS=$controller_public_ip|' \ -e 's|CONFIG_NEUTRON_INSTALL=n|CONFIG_NEUTRON_INSTALL=y|' \ -e 's|CONFIG_SWIFT_INSTALL=n|CONFIG_SWIFT_INSTALL=y|' \ -e 's|CONFIG_NEUTRON_USE_NAMESPACES=n|CONFIG_NEUTRON_USE_NAMESPACES=y|' \ -e 's|CONFIG_SSH_KEY=.*|CONFIG_SSH_KEY=/root/.ssh/id_rsa.pub|' \ -e 's|CONFIG_NOVA_COMPUTE_HOSTS=.*|CONFIG_NOVA_COMPUTE_HOSTS=$compute_public_ip|' \ -e 's|CONFIG_NEUTRON_OVS_TENANT_NETWORK_TYPE=.*|CONFIG_NEUTRON_OVS_TENANT_NETWORK_TYPE=gre|' \ -e 's|CONFIG_NEUTRON_OVS_VLAN_RANGES=.*|CONFIG_NEUTRON_OVS_VLAN_RANGES=phynet1|' \ -e 's|CONFIG_NEUTRON_OVS_TUNNEL_RANGES=.*|CONFIG_NEUTRON_OVS_TUNNEL_RANGES=1:1000|' \ -e 's|CONFIG_NEUTRON_OVS_TUNNEL_IF=.*|CONFIG_NEUTRON_OVS_TUNNEL_IF=eth1|' \ -e 's|_PW=.*|_PW=redhat|g' \ -i /root/packstack_config.txt The following error occurs.. 00:05:57.866 ERROR : Error during puppet run : Error: Local ip for ovs agent must be set when tunneling is enabled at /var/tmp/packstack/94c2dbe51aa8420086bcccbc197a8775/modules/neutron/manifests/agents/ovs.pp:28 on node localhost.localdomain I was unable to get the logs.. will attach them when I can.
default puppet that ships w/ fedora 19 may be part of the issue here. Francesco Vollero has this working w/ the puppet version from puppet labs on f19.
> Francesco Vollero has this working w/ the puppet version from puppet labs on > f19. What are the puppet NVRs f19 vs puppetlabs? Please also compare facter versions, since this sounds actually like a facter issue not puppet.
Puppet Labs: Installed: puppet-3.3.1-1.fc19.noarch Installed: 1:facter-1.7.3-1.fc19.x86_64 F19 Repo: puppet-3.1.1-7.fc19.noarch.rpm facter-1.6.18-4.fc19.x86_64.rpm Noticed this in the logs.. ip_neutron.pp # Create firewall rules to allow only the hosts that need to connect # to neutron $hosts = [ '192.168.200.198','192.168.200.145' ] define add_allow_host { firewall { "001 neutron incoming ${title}": proto => 'tcp', dport => ['9696'], action => 'accept', source => $title, } } add_allow_host { $hosts:} if "eth1" { $localip = $ipaddress_eth1 } else { $localip = '192.168.200.145' } class { 'neutron::agents::ovs': enable_tunneling => true, local_ip => $localip, }
FYI.. biosdevname is turned off in the test env. http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming
This is absolutely a puppet 1.6.x vs. puppet 1.7.x issue. Puppet 1.6.x does not generate the "ipaddress_<interface>" facts. E.g.: # rpm -q facter facter-1.6.18-4.fc19.x86_64 # ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether fa:16:3e:35:ab:44 brd ff:ff:ff:ff:ff:ff inet 10.0.0.2/24 brd 10.0.0.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fe35:ab44/64 scope link valid_lft forever preferred_lft forever # facter | grep ipaddress ipaddress => 10.0.0.2 But if I upgrade to facter from the PuppetLabs repo: # rpm -q facter facter-1.7.4-1.fc19.x86_64 # facter | grep ipaddress ipaddress => 10.0.0.2 ipaddress_eth0 => 10.0.0.2 ipaddress_lo => 127.0.0.1 [root@test0 ~]#
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.