Hello all, I am trying to resolve a critical error when fixed_range='' is specified in nova.conf.
The error is resolved if I set fixed_range manually, i.e. fixed_range= 10.0.0.0/24 VM launching via Horizon and guest networking is fully operational with the above fix. Similar error but different cause, https://lists.launchpad.net/openstack/msg04588.html I am using FlatDHCP networking between two Openstack nodes running the Folsom release (from EPEL) on a base installation of Scientific Linux 6.4. I followed the guide from Red Hat Openstack Getting Started guide to prepare Keystone, Glance and Horizon and the Compute manual for setting up the networking. Controller node (Keystone, Nova, Glance, Horizon) "sl1": 10.168.2.122 Compute only node "compute1": 10.168.2.126 Iptables disabled (service iptables stop on both nodes). Every service except nova-network seems to be operational, judging from openstack-status and service --status-all | grep openstack. nova.conf snippet on the controller node: network_manager = nova.network.manager.FlatDHCPManager flat_interface = eth2 public_interface = eth1 my_ip = 10.168.2.122 #fixed_range=10.0.0.0/24 #fixed_range='' flat_network_bridge = br100 flat_injected = False nova.conf snippet on the compute only node: network_manager = nova.network.manager.FlatDHCPManager flat_interface = eth1 public_interface = eth0 my_ip = 10.168.2.126 #fixed_range = 10.0.0.0/24 #fixed_range = '' flat_network_bridge = br100 flat_injected = False s3_host = 10.168.2.122 ec2_host = 10.168.2.122 qpid_hostname = 10.168.2.122 metadata_host = 10.168.2.122 ec2_dmz_host = 10.168.2.122 glance_api_servers=sl1:9292 nova-network.log (identical on both nodes): 2013-05-22 16:21:17 18884 AUDIT nova.service [-] Starting network node (version 2012.2.3-1.el6) 2013-05-22 16:21:22 18884 CRITICAL nova [-] Unexpected error while running command. Command: sudo nova-rootwrap /etc/nova/rootwrap.conf iptables-restore -c Exit code: 2 Stdout: '' Stderr: "Bad argument `SNAT'\nError occurred at line: 27\nTry `iptables-restore -h' or 'iptables-restore --help' for more information.\n" Any suggestions on how to resolve this issue would be much appreciated! Justin
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
