Ask Your Question
0

Error using: /usr/bin/packstack --allinone

asked 2014-12-03 10:14:47 -0600

Stuart gravatar image

updated 2014-12-03 10:18:57 -0600

dbaxps gravatar image

Hello

I am installing on a single server using this command: /usr/bin/packstack --allinone

The installation runs through until this error:

192.168.1.55_neutron.pp:                         [ ERROR ]
Applying Puppet manifests                         [ ERROR ]

ERROR : Error appeared during Puppet run: 192.168.1.55_neutron.pp
Error: Could not start Service[neutron-ovs-agent-service]:  
       Execution of '/usr/bin/systemctl start neutron-openvswitch-agent' returned 6:
       Failed to issue method call: Unit neutron-openvswitch-agent.service failed to load: No such file or directory.

You will find full trace in log:    
                                   /var/tmp/packstack/20141203-143411-A9IT8v/manifests/192.168.1.55_neutron.pp.log
Please check log file:    /var/tmp/packstack/20141203-143411-A9IT8v/openstack-setup.log

Looking in the log files I can see these messages:

=======
Log 1:    /var/tmp/packstack/20141203-143411-A9IT8v/manifests/192.168.1.55_neutron.pp.log:
-----------------------
Notice:   /Stage[main]/Neutron::Agents::Ml2::Ovs/Neutron_plugin_ovs[agent/arp_responder]/ensure: created
Error:      Could not start Service[neutron-ovs-agent-service]:
Execution of     '/usr/bin/systemctl start neutron-openvswitch-agent' returned 6:
Failed to issue method call: Unit neutron-openvswitch-agent.service
failed to load: No such file or directory.

Wrapped exception:
Execution of '/usr/bin/systemctl start neutron-openvswitch-agent' returned 6: Failed to issue method call:
Unit neutron-openvswitch-agent.service failed to load: No such file or directory.

Error:   /Stage[main]/Neutron::Agents::Ml2::Ovs/Service[neutron-ovs-agent-service]/ensure:
                       change from stopped to running
failed:  Could not start Service[neutron-ovs-agent-service]: Execution of '/usr/bin/systemctl start neutron-openvswitch-agent' returned 6: Failed to issue method call:
      Unit neutron-openvswitch-agent.service failed to load: No such file or directory.
Notice: /Stage[main]/Neutron::Agents::Ml2::Ovs/Service[neutron-ovs-agent-service]:
   Triggered 'refresh' from 11 events
Notice:    /Stage[main]/Main/Vs_bridge[br-ex]: Dependency Service[neutron-ovs-agent-service] has failures: true
Warning: /Stage[main]/Main/Vs_bridge[br-ex]: Skipping because of failed dependencies
Notice:    /Stage[main]/Neutron::Server/Neutron_config[keystone_authtoken/admin_user]/ensure: created

Log 2: /var/tmp/packstack/20141203-143411-A9IT8v/manifests/192.168.1.55_neutron.pp.log:

-----------------------
PuppetError: Error appeared during Puppet run: 192.168.1.55_neutron.pp
Error:     Could not start Service[neutron-ovs-agent-service]:
 Execution of     '/usr/bin/systemctl start neutron-openvswitch-agent' returned 6: Failed to issue method call: Unit neutron-openvswitch-agent.service failed to load: No such file or directory.
You will find full trace in log /var/tmp/packstack/20141203-143411-A9IT8v/manifests/192.168.1.55_neutron.pp.log

Which seems to be a bug affecting this: /usr/bin/systemctl start neutron-openvswitch-agent

However, at the command line it works:

# /usr/bin/systemctl stop neutron-openvswitch-agent
# /usr/bin/systemctl start neutron-openvswitch-agent
# /usr/bin/systemctl status neutron-openvswitch-agent
neutron-openvswitch-agent.service - OpenStack Neutron Open vSwitch Agent
      Loaded: loaded (/usr/lib/systemd/system/neutron-openvswitch-agent.service; disabled)
      Active: active (running) since Wed 2014-12-03 16:11:13 GMT; 3s ago
      Main PID: 9854 (neutron-openvsw)
      CGroup: /system.slice/neutron-openvswitch-agent.service
      ââ9854 /usr/bin/python /usr/bin/neutron-openvswitch-agent --config-file
                    /usr/share/neutron/neutron-dist.conf --config-file /etc/neutron...
      ââ9948 sudo neutron-rootwrap /etc/neutron/rootwrap.conf ovsdb-client monitor Interface 
                    name,ofport --format=json
      ââ9949 /usr/bin/python /usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf ovsdb-client 
                monitor Interface name,ofport --format=json
      ââ9953 /bin/ovsdb-client monitor Interface name,ofport --format=json

Dec 03 16:11:15 OpStck-1 sudo[9936]: neutron : TTY ...
(more)
edit retag flag offensive close merge delete

Comments

Sorry about the formatting. This wiki does not seem to be able to handle Carriage Returns very well.

Stuart gravatar imageStuart ( 2014-12-03 10:15:56 -0600 )edit

NOTE: installed on a new installation that has never seen OpenStack before

Stuart gravatar imageStuart ( 2014-12-03 10:17:29 -0600 )edit

I'm seeing the same thing on a clean CentOS 7 enviroment. 'packstack --allinone' works fine, but 'packstack --allinone --provision-all-in-one-ovs-bridge=n' causes the above error.

kitplummer gravatar imagekitplummer ( 2014-12-04 10:05:58 -0600 )edit

Hi, have u first generated the packstack answer file with command..then did u run that answer file..? If there is error u can rerun and check out?

Praveen N gravatar imagePraveen N ( 2015-03-10 06:02:05 -0600 )edit

3 answers

Sort by » oldest newest most voted
1

answered 2014-12-03 14:09:46 -0600

Stuart gravatar image

I am going to answer my own question.

I have found that on a clean installation (CentOS 7 in this case) if the packstack script fails with errors (usually Puppet errors but the specific Puppet error changes to be for different applications) then the below has worked for me:

Run this: /usr/bin/packstack --answer-file=/root/packstack-AnswerFile.cfg

If this also fails, then run this below (it will however fail with network errors but no Puppet errors). /usr/bin/packstack --gen-answer-file=/root/packstack-AnswerFile.cfg /usr/bin/packstack --answer-file=/root/packstack-AnswerFile.cfg

edit flag offensive delete link more
0

answered 2015-09-17 09:37:29 -0600

nzrtp gravatar image

What is the solution to the above issue ? I am facing similar issue with OSP7 install on multi device (1 Controller, 2 Compute). Would appreciate if someone can point out what could be the cause.

172.18.7.9_nova.pp: [ DONE ] 172.18.7.16_nova.pp: [ DONE ] 172.18.7.17_nova.pp: [ DONE ] Applying 172.18.7.16_neutron.pp Applying 172.18.7.17_neutron.pp Applying 172.18.7.9_neutron.pp 172.18.7.9_neutron.pp: [ ERROR ] Applying Puppet manifests [ ERROR ]

ERROR : Error appeared during Puppet run: 172.18.7.9_neutron.pp Error: Could not apply complete catalog: Found 1 dependency cycle: You will find full trace in log /var/tmp/packstack/20150917-060958-oFHGnx/manifests/172.18.7.9_neutron.pp.log Please check log file /var/tmp/packstack/20150917-060958-oFHGnx/openstack-setup.log for more information Additional information: * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components. * File /root/keystonerc_admin has been created on OpenStack client host 172.18.7.9. To use the command line tools you need to source the file. * To access the OpenStack Dashboard browse to http://172.18.7.9/dashboard . Please, find your login credentials stored in the keystonerc_admin in your home directory. * To use Nagios, browse to http://172.18.7.9/nagios username: nagiosadmin, password:

edit flag offensive delete link more
0

answered 2014-12-03 10:54:55 -0600

mpetason gravatar image

Verify you are running this on the correct OS. There are bugs that are similar for packstack that refer to a different process with the same error:

https://bugs.launchpad.net/packstack/...

You could also submit a new bug if you do not think that this covers your actual issue:

https://bugs.launchpad.net/packstack

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

2 followers

Stats

Asked: 2014-12-03 10:14:47 -0600

Seen: 2,326 times

Last updated: Dec 03 '14