Bug 1302667 - [FC23] engine-setup fails to configure nfs
Summary: [FC23] engine-setup fails to configure nfs
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Setup.Engine
Version: 3.6.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.0.0-alpha
: 4.0.0
Assignee: Yedidyah Bar David
QA Contact: Pavel Stehlik
Depends On:
TreeView+ depends on / blocked
Reported: 2016-01-28 11:00 UTC by Yedidyah Bar David
Modified: 2016-07-26 10:44 UTC (History)
9 users (show)

Fixed In Version: ovirt 4.0.0 alpha1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-07-26 10:44:13 UTC
oVirt Team: Integration
sbonazzo: ovirt-4.0.0?
ylavi: Triaged?
ylavi: planning_ack+
sbonazzo: devel_ack+
rule-engine: testing_ack?

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
oVirt gerrit 54988 0 master MERGED packaging: setup: Stop nfs-config service if changing config 2016-03-21 14:05:46 UTC

Description Yedidyah Bar David 2016-01-28 11:00:39 UTC
Description of problem:

On recent fedora, there is a new service called nfs-config, which copies configuration from /etc/sysconfig/nfs to /run/sysconfig/nfs-utils . All the nfs services are configured to run after it, and read their env/conf from the copy.

We need, therefore, to also restart nfs-config prior to restarting the other services.

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

Not sure, happened to me on fedora 23

How reproducible:


Steps to Reproduce:
1. Install a new fedora 23 machine
2. install and setup a recent ovirt-engine, choose to configure nfs iso domain

Actual results:

mounts from another machine fail

'rpcinfo -p' shows that mountd listens on 20048 (default) and not 892 (ovirt-setup default)

Expected results:

mounts succeed

Additional info:

Comment 1 Yedidyah Bar David 2016-01-28 11:01:39 UTC

service nfs-config stop
service nfs-config start
service nfs stop
service nfs start

Comment 2 Lukas Svaty 2016-07-26 10:44:13 UTC
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA

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