'.' in ethernet device name causing packstack parse error

asked 2014-01-21 18:51:49 -0500

tomwaterhouse
11 ●2 ●2 ●2

updated 2014-01-24 18:38:05 -0500

smaffulli
6886 ●36 ●67 ●100 http://maffulli.net/

I am attempting to install Havana with GRE in a multi-node environment. My data network device is eth1.1200. I get the following error when the neutron script is being run.

 Error: Could not parse for environment production: Syntax error at '.'; expected '}' at /var/tmp/packstack/f8e1377ccde54cb3af8320b1ca559833/manifests/10.93.235.86_neutron.pp:31

I haven't been able to find any information regarding this issue. I believe the offending lines in neutron.pp are:

if "eth1.1200" {
  $localip = $ipaddress_eth1.1200
} else {
  $localip = '10.93.235.86'
}

Before I log a bug I'm hoping someone can tell me this should work, or offer up a work-around.

Cheers,

Tom

Comments

If you run "facter" on this system, what does the "ipaddress_<interfacename>" fact look like for this interface?

larsks ( 2014-01-24 08:59:17 -0500 )edit

add a comment

answered 2014-01-25 17:26:54 -0500

larsks
5269 ●20 ●57 ●98 http://redhat.com/

You didn't say, but I'm guessing that you're installing using packstack with a configuration that looks something like:

CONFIG_NEUTRON_OVS_TUNNEL_IF=eth1.1200

Facter (version 1.7 or later) generates facts for each interface on your system of the form ipaddress_<interfacename>. When there is a . or other character in the name that would result in an invalid fact name, facter replaces that character with _. So, for example, on your system I would expect to see:

ipaddress_eth1_1200=...

In theory, if you set CONFIG_NEUTRON_OVS_TUNNEL_IF=eth1_1200, things should work as you expect. The Puppet modules used by packstack should take care of this automatically; I will take a look at fixing this so that no workaround is necessary.

edit flag offensive delete link

add a comment

'.' in ethernet device name causing packstack parse error

Comments

1 answer

Your Answer

Get to know Ask OpenStack

Question Tools

Stats

Related questions

Feedback About This Page

OpenStack

Community

Documentation

Branding & Legal