Bug 1154149 - engine-setup fails to start nfs server on a Fedora 20 minimal installation
Summary: engine-setup fails to start nfs server on a Fedora 20 minimal installation
Keywords:
Status: CLOSED DUPLICATE of bug 1163395
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-installer
Version: 3.5
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 3.5.1
Assignee: Sandro Bonazzola
QA Contact: Pavel Stehlik
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-17 16:42 UTC by Jakob Gillich
Modified: 2014-11-27 08:48 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-11-05 12:26:10 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)

Description Jakob Gillich 2014-10-17 16:42:17 UTC
Description of problem:

After installing a fresh copy of Fedora 20 using a netinstall iso with the minimal package set, engine-setup fails to configure the NFS server.

I selected an nfs3 server for the ISO domain.

The ovirt-engine log file contains the following:

2014-10-17 18:16:43 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:861 execute-output: ('/bin/systemctl', 'start', 'nfs-server.service') stdout:


2014-10-17 18:16:43 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:866 execute-output: ('/bin/systemctl', 'start', 'nfs-server.service') stderr:
Job for nfs-server.service failed. See 'systemctl status nfs-server.service' and 'journalctl -xn' for details.

2014-10-17 18:16:43 DEBUG otopi.context context._executeMethod:152 method exception
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in _executeMethod
    method['method']()
  File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/system/nfs.py", line 277, in _closeup
    state=state,
  File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 138, in state
    'start' if state else 'stop'
  File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 77, in _executeServiceCommand
    raiseOnError=raiseOnError
  File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 871, in execute
    command=args[0],
RuntimeError: Command '/bin/systemctl' failed to execute
2014-10-17 18:16:43 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Closing up': Command '/bin/systemctl' failed to execute

Output of systemctl status nfs-server:

nfs-server.service - NFS Server
   Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled)
   Active: failed (Result: exit-code) since Fri 2014-10-17 18:16:43 CEST; 18min ago
  Process: 13368 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILURE)
  Process: 13362 ExecStartPre=/usr/libexec/nfs-utils/scripts/nfs-server.preconfig (code=exited, status=0/SUCCESS)

Oct 17 18:16:43 ovirt.localdomain systemd[1]: Starting NFS Server...
Oct 17 18:16:43 ovirt.localdomain exportfs[13368]: exportfs: ovirt.localdomain:/var/lib/exports/iso: Function not implemented
Oct 17 18:16:43 ovirt.localdomain systemd[1]: nfs-server.service: control process exited, code=exited status=1
Oct 17 18:16:43 ovirt.localdomain systemd[1]: Failed to start NFS Server.
Oct 17 18:16:43 ovirt.localdomain systemd[1]: Unit nfs-server.service entered failed state.


Content of /etc/exports.d/ovirt-engine-iso-domain.exports:

/var/lib/exports/iso	ovirt.localdomain(rw)


Version-Release number of selected component (if applicable): 3.5.0.1-1.fc20


How reproducible: -


Steps to Reproduce:
1. Install Fedora 20 minimal
2. Install oVirt All-In-One
3. Run engine-setup and pick the default settings

Comment 1 Sandro Bonazzola 2014-10-20 15:30:43 UTC
Hi Jakob, I'm not really sure this is an ovirt bug.
Looking at your report above, the failing command is:

Process: 13368 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILURE)

and the error output is:

Oct 17 18:16:43 ovirt.localdomain exportfs[13368]: exportfs: ovirt.localdomain:/var/lib/exports/iso: Function not implemented

And as far as I know the "function not implemented" is supposed to mean that the nfs kernel server module isn't loaded.

We'll try to reproduce, can you check your system config? It may be a configuration error caused by anaconda.

Comment 2 Sandro Bonazzola 2014-11-05 12:26:10 UTC
Please reopen if more info can be provided for reproducing the issue.

Comment 3 Yedidyah Bar David 2014-11-27 08:48:10 UTC

*** This bug has been marked as a duplicate of bug 1163395 ***


Note You need to log in before you can comment on or make changes to this bug.