Ask Your Question

OVS Primary Controller Puppet Manifest Issue

asked 2016-05-07 04:47:09 -0800

bossbeasley gravatar image

updated 2016-05-08 00:15:06 -0800

Hi - pls can someone help with this one:

Installing Bramahputra - 3 controllers, 2 compute nodes.

Create openstack environment - ok Deploy - Ubuntu OS installs OK. OVS Primary Controller install begins -

Puppet tries to pull the package from the incorrect IP address. The IP network of my admn/pxe network is

Puppet is trying to pull the OVS package from as seen in the puppet log below:

(Execinstall dpdk ) Executing 'wget ; bash ./ eth2'

However - is the wrong IP address. This is the default IP address which Fuel assigns during install which I have changed in my network. I am using network - this is my PXE Admin network and puppet should be issuing a WGET to instead.

Basically it looks like the plugin install scripts and puppet manifests have static IP addresses set for - meaning that for the install to work you have to use the 10.20.x.x network, or somehow when the plugins are installed into FUEL the install scripts and manifests are picking up the address from the environement (even though I don't have this address configured anywhere in my environment).

Eventually the install times out (as one would expect) with the following:

[447] Error running RPC method granulardeploy: Failed to execute hook 'ovsinstallprimarycontroller' Puppet run failed. Check puppet logs for details

priority: 2400 failonerror: true uids: - '6' parameters: puppetmodules: puppet/modules:/etc/puppet/modules puppetmanifest: puppet/manifests/ovs-install-primary-controller.pp timeout: 720 cwd: /etc/fuel/plugins/fuel-plugin-ovs-0.5/ type: puppet id: ovsinstallprimarycontroller diagnosticname: fuel-plugin-ovs-0.5.2 , trace: ["/usr/share/gems/gems/astute-8.0.0/lib/astute/nailgunhooks.rb:64:in block in process'", "/usr/share/gems/gems/astute-8.0.0/lib/astute/nailgun_hooks.rb:26:ineach'", "/usr/share/gems/gems/astute-8.0.0/lib/astute/nailgunhooks.rb:26:in process'", "/usr/share/gems/gems/astute-8.0.0/lib/astute/deployment_engine/granular_deployment.rb:215:inpredeploymentactions'", "/usr/share/gems/gems/astute-8.0.0/lib/astute/deploymentengine.rb:36:in deploy'", "/usr/share/gems/gems/astute-8.0.0/lib/astute/orchestrator.rb:216:indeploycluster'", "/usr/share/gems/gems/astute-8.0.0/lib/astute/orchestrator.rb:52:in granular_deploy'", "/usr/share/gems/gems/astute-8.0.0/lib/astute/server/dispatcher.rb:92:ingranulardeploy'", "/usr/share/gems/gems/astute-8.0.0/lib/astute/server/server.rb:189:in dispatch_message'", "/usr/share/gems/gems/astute-8.0.0/lib/astute/server/server.rb:146:inblock in dispatch'", "/usr/share/gems/gems/astute-8.0.0/lib/astute/server/taskqueue.rb:64:in call'", "/usr/share/gems/gems/astute-8.0.0/lib/astute/server/task_queue.rb:64:inblock in each'", "/usr/share/gems/gems/astute-8.0.0/lib/astute/server ... (more)

edit retag flag offensive close merge delete


The workaround for this is to edit the install scripts and manifests and replace the IP address with the correct one for the environment. Re-run deploy, and then it works.

bossbeasley ( 2016-05-08 00:15:55 -0800 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2016-05-09 04:00:26 -0800

lmcdasm gravatar image

Hey there.

looking at your issue, I think you have hit on a bug with the OVS Plugin for sure - since you are right, the default values are there. I suspect the plugin that is used, is not "sourcing" the deploy.yaml files for getting the correct address. I suspect that Billy and the Intel guys - who develop the plugin, have simply forgot to add the check.

To that end I have created a FUEL JIRA ticket and copied your information above therein, and assigned it to the OVS guys. you can find the ticket here.

Cheers, Daniel

edit flag offensive delete link more


Thanks Daniel - worked around it myself for now.

bossbeasley ( 2016-05-09 05:02:58 -0800 )edit

Great. however, i still want this fixed. Billy O' from Intel (the owner) has asked some questions in the JIRA ticket, if you can take a look - since we would want to figure out what happened as there is code to deal with this and it would be great for the community at large to sort it out. Thx,D

lmcdasm ( 2016-05-09 06:12:25 -0800 )edit

No probs - will take a look

bossbeasley ( 2016-05-09 23:47:06 -0800 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Question Tools

1 follower


Asked: 2016-05-07 04:47:09 -0800

Seen: 171 times

Last updated: May 09 '16