Bug 840798 - Runlevel editor can not start nfs and rpcbind properly
Summary: Runlevel editor can not start nfs and rpcbind properly
Status: RESOLVED DUPLICATE of bug 799471
Alias: None
Product: openSUSE 12.3
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: IA64 openSUSE 12.3
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-17 10:31 UTC by Krasimir Ivanov
Modified: 2013-09-27 15:46 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Screenshot from the runlevel editor (212.93 KB, image/png)
2013-09-17 10:31 UTC, Krasimir Ivanov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Krasimir Ivanov 2013-09-17 10:31:16 UTC
Created attachment 558574 [details]
Screenshot from the runlevel editor

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0

I am using some NFS mounted resources from a server. Unfortunately mount script stop to work properly after upgrade to openSUSE 12.3.
I found that during startup of the computer NFS is started not properly (has Yes* in the runlevel editor). 
I try to start nfs manually from the runlevel editor but it starts with some error and again has Yes* in the listing.
After some research I found the reason for it - it happens because rpcbind was not started properly (also has 'Yes*' in the listing).
When i start manually first rpcbind and just then the nfs bot start as expected and work well. (After it I can mount my NFS shares as expected)
So I believe if the startup process of openSUSE 12.3 will start first rpcbind and only after it the nfs every thing with NFS will be OK.

Reproducible: Always

Steps to Reproduce:
1. Open the run level editor and enable nfs and rpcbind
2. Shutdown the computer and after it start again
3. Open again the run level editor and you will see in the listing of the services nfs and rpcbind are marked with 'Yes*'
4. Start manually there first rpcbind and only after it nfs. If done so nfs start working well until the new restart of the computer 
Actual Results:  
Open again the run level editor and you will see in the listing of the services nfs and rpcbind are marked with 'Yes*'
NFS shares could not be mounted during the startup of the computer.

Expected Results:  
I expect to see in the run level editor in the listing of the services nfs and rpcbind are marked with 'Yes' and NFS share get mounted during startup of the computer.
Comment 1 Josef Reidinger 2013-09-27 15:46:24 UTC
have all related problems with systemd in runlevel in one place

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