Bug 1038601 - Packstack fails because neutron fails to start "Please make sure that the zfs-fuse daemon is running."
Summary: Packstack fails because neutron fails to start "Please make sure that the zfs...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: RDO
Classification: Community
Component: openstack-neutron
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-05 13:05 UTC by Richard W.M. Jones
Modified: 2016-04-26 16:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-16 11:12:08 UTC

Attachments (Terms of Use)
openstack-setup.log (16.09 KB, text/plain)
2013-12-05 13:07 UTC, Richard W.M. Jones 		no flags Details
192.168.0.134_neutron.pp.log (14.69 KB, text/plain)
2013-12-05 13:08 UTC, Richard W.M. Jones 		no flags Details
192.168.0.134_keystone.pp.log (11.65 KB, text/plain)
2013-12-05 13:18 UTC, Richard W.M. Jones 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Richard W.M. Jones 2013-12-05 13:05:41 UTC 
Description of problem:

Fresh install of Packstack on top of fresh install of Fedora 19.

Packstack fails to complete because neutron has problems
starting up.  See the attached log files.

Version-Release number of selected component (if applicable):

openstack-neutron-2013.2-2.fc20.noarch
(I don't know why "fc20" is there, it's definitely an F19 host).

How reproducible:

At least once.
Comment 1 Richard W.M. Jones 2013-12-05 13:07:34 UTC 
Created attachment 833142 [details]
openstack-setup.log
Comment 2 Richard W.M. Jones 2013-12-05 13:08:12 UTC 
Created attachment 833143 [details]
192.168.0.134_neutron.pp.log
Comment 3 Richard W.M. Jones 2013-12-05 13:18:01 UTC 
Created attachment 833145 [details]
192.168.0.134_keystone.pp.log

Strange .. this affects keystone too (even though keystone was working
before).
Comment 4 Alan Pevec 2013-12-05 13:31:03 UTC 
> (I don't know why "fc20" is there, it's definitely an F19 host).

RDO Havana for F19 == regular F20 Havana builds really in a convenience repo
We'll do that until N and N+1 Fedora keep compatible enough Python runtimes.
Comment 5 Richard W.M. Jones 2013-12-05 13:45:08 UTC 
Manually starting the zfs-fuse service (ie. service zfs-fuse start)
has removed these warnings/errors.
Comment 6 Lars Kellogg-Stedman 2014-02-10 18:48:35 UTC 
The ZFS related errors can be ignored.  That's chatter produced by Puppet that has no operational impact.

Looking at 192.168.0.134_neutron.pp.log, I see:

  Error: Could not start Service[openvswitch]: Execution of '/sbin/service openvswitch start' returned 1: 
Error: /Stage[main]/Vswitch::Ovs/Service[openvswitch]/ensure: change from stopped to running failed: Could not start Service[openvswitch]: Execution of '/sbin/service openvswitch start' returned 1: 

...which causes everything else to fail that has a dependency on Service[openvswitch].

Do you have any logs that indicate why openvswitch failed to start (possibly /var/log/messages)?

For Keystone, all the errors are of the form:

  Error: /Stage[main]/Keystone::Roles::Admin/Keystone_role[_member_]: Could not evaluate: Execution of '/u
sr/bin/keystone --endpoint http://127.0.0.1:35357/v2.0/ role-list' returned 1: Service Unavailable (HTTP
 503)


...which suggests that the keystone service failed to start.  Is there anything of interest in /var/log/keystone/keystone.log?
Comment 7 Richard W.M. Jones 2014-06-16 11:12:08 UTC 
As I don't have this machine any longer, I'm closing this bug.
Note You need to log in before you can comment on or make changes to this bug.