Bug 853914 - [rhevm-setup] failure to create the local nfs share if nfsd is already started
[rhevm-setup] failure to create the local nfs share if nfsd is already started
Status: CLOSED INSUFFICIENT_DATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup (Show other bugs)
3.1.0
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Alon Bar-Lev
Pavel Stehlik
integration
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-03 06:13 EDT by Simon Grinberg
Modified: 2015-09-22 09 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-09-03 09:06:37 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Simon Grinberg 2012-09-03 06:13:46 EDT
Description of problem:
The script assumes that nfs is stopped and only tries to start it. This may not be the case like in my setup where I've reused existing machine. 

The mount point created correctly
The entry was added to the /etc/exports file
Then installation failed. 

Version-Release number of selected component (if applicable):
SI16
rhevm-setup-3.1.0-14.el6ev.noarch

How reproducible:


Steps to Reproduce:
1. start the nfs service 
2. rhevm-setup 
3. Answer yes for: Configure NFS share on this server to be used as an ISO Domain? ['yes'| 'no']  [yes] : 
  
Actual results:
Installation will fail due to ISO domain creation failure. 

Expected results:
Request to stop the service if it's already running 

Additional info:
2012-09-03 12:32:33::DEBUG::common_utils::320::root:: stderr = 
2012-09-03 12:32:33::DEBUG::common_utils::321::root:: retcode = 1
2012-09-03 12:32:33::ERROR::rhevm-setup::1658::root:: Traceback (most recent call last):
  File "/usr/bin/rhevm-setup", line 1656, in _startNfsServices
    srv.start(True)
  File "/usr/share/ovirt-engine/scripts/common_utils.py", line 1006, in start
    raise Exception(output_messages.ERR_FAILED_START_SERVICE % self.name)
Exception: Error: Can't start the nfs service

2012-09-03 12:32:33::ERROR::rhevm-setup::1615::root:: Traceback (most recent call last):
  File "/usr/bin/rhevm-setup", line 1601, in _configNfsShare
    _startNfsServices()
  File "/usr/bin/rhevm-setup", line 1659, in _startNfsServices
    raise Exception(output_messages.ERR_FAILED_TO_START_NFS_SERVICE)
Exception: Failed to start the NFS services

2012-09-03 12:32:33::DEBUG::setup_sequences::62::root:: Traceback (most recent call last):
  File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line 60, in run
    function()
  File "/usr/bin/rhevm-setup", line 1616, in _configNfsShare
    raise Exception(output_messages.ERR_FAILED_CFG_NFS_SHARE)
Exception: Failed to configure NFS share on this host
Comment 1 Itamar Heim 2012-09-03 06:38:24 EDT
wouldn't reload work and should be done if service is already up?
Comment 2 Alon Bar-Lev 2012-09-03 06:46:36 EDT
(In reply to comment #1)
> wouldn't reload work and should be done if service is already up?

Yes.
Comment 3 Alon Bar-Lev 2012-09-03 07:07:17 EDT
Regardless of it is better to use reload when service is up.

Looking at the code it is always stop before start, while ignoring stop result.

I could not reproduce this on upstream and downstream.

Simon, if it is reproducible at your machine I will be happy to investigate.
Comment 4 Simon Grinberg 2012-09-03 08:37:48 EDT
Alon, 

Unfortunately in the last couple of days, I've been spending too much time on debug or showing issues on my system. I only have two more days to prepare my work thus I can't afford more delays. 

I'll try to recreate for you in two weeks, I don't see this as urgent. 

Alternatively this may be a race (do to not waiting for the stop to succeed) so here is some more info: 

1. I did this on a VM.
2. In the exports files there was already an exported directory. This means the nfs did had something to export. This may delay the stop since it may need to verify there are no users first.

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