Ask Your Question
0

Packstack --allinone hangs during neutron.pp

asked 2014-05-29 12:38:39 -0500

StephanieMason gravatar image

I created a RHEL 6.5 vm with 2 cpus and 4G RAM one nic in our vcenter environment and followed the steps on the quick start page.

I have done this now 3 times. Each time my packstack hangs during the configuration of the Applying 10.250.0.169_neutron.pp process. When I look at the Running file for Applying 10.250.0.169_neutron.pp the last few ,lines of the file are :

Notice: /Stage[main]/Neutron::Plugins::Ovs/File[/etc/neutron/plugin.ini]/ensure: created Notice: /Stage[main]/Packstack::Neutron::Bridge/File_line[/etc/sysctl.conf bridge-nf-call-ip6tables]/ensure: created Notice: /Stage[main]/Packstack::Neutron::Bridge/File_line[/etc/sysctl.conf bridge-nf-call-iptables]/ensure: created Notice: /Stage[main]/Packstack::Neutron::Bridge/File_line[/etc/sysctl.conf bridge-nf-call-arptables]/ensure: created Notice: /Stage[main]/Neutron/Neutron_config[DEFAULT/rabbit_hosts]/ensure: created Notice: /Stage[main]/Neutron::Agents::Dhcp/Neutron_dhcp_agent_config[DEFAULT/state_path]/ensure: created Notice: /Stage[main]/Neutron/Neutron_config[DEFAULT/allow_pagination]/ensure: created Notice: /Stage[main]/Neutron/Neutron_config[DEFAULT/dhcp_lease_duration]/ensure: created Notice: /Stage[main]/Neutron::Agents::Ovs/Neutron_plugin_ovs[OVS/enable_tunneling]/ensure: created Notice: /Stage[main]/Neutron::Agents::Ovs/Neutron_plugin_ovs[OVS/integration_bridge]/ensure: created

Looking at a process list shows that /usr/bin/ovs-vsctl add-br br-int was spawned by the puppet process and is just hanging out. If I kill that task, the puppet process notes an error on the bridge creation and the installation fails. If I try to run the /usr/bin/ovs-vsctl add-br br-int command manually it says that one already exists. I have exhausted my google fu on this. Do you have any idea what may be going on? From what I can see the packstack install process should be fairly straight forward.

Any insight you can provide is greatly appreciated.

edit retag flag offensive close merge delete

Comments

Run ovs-vsctl show and verify does br-int exist now or not ?

dbaxps gravatar imagedbaxps ( 2014-05-29 12:54:48 -0500 )edit

I believe that you have to clean up existing ovs-vsctl show ouput via commands:-
$ ovs-vsctl --help| grep del | grep BRIDGE
del-br BRIDGE delete BRIDGE and all of its ports
del-port [BRIDGE] PORT delete PORT (which may be bonded) from BRIDGE
Then run :-
$ setenforce 0
Try packstack with old answer-file again and see what happens .

dbaxps gravatar imagedbaxps ( 2014-05-29 21:28:10 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-05-30 04:36:48 -0500

DanIzack gravatar image

updated 2014-05-30 04:39:09 -0500

Clean up existing OVS configuration
$ ovs-vsctl show
will report you all OVS bridges, remove them with `ovs-vsctl del-br bridge-name`.
Set SELINUX to permissive
$ packstack --answer-file=previous-answer-file.txt ( the one produced by unsuccessful run)
Keep installation log to analyze in case of failure
edit flag offensive delete link more

Your Answer

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

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-05-29 12:38:39 -0500

Seen: 874 times

Last updated: May 30 '14