Hide Forgot
NETWORKING is set to no in /etc/sysconfig/network until networking has been configured at which point it's set to yes. This means that the rpcbind and nfslock services are not started on bootup. After network configuration is competed and NETWORKING is set to yes we should start these services.
Here are all services checking if network is configured before starting up, we should start them all: # grep NETWORKING /etc/rc3.d/S* /etc/rc3.d/S10network:[ "${NETWORKING}" = "no" ] && exit 6 /etc/rc3.d/S13rpcbind: [ "$NETWORKING" = "yes" ] || exit 6 /etc/rc3.d/S14nfslock: [ "${NETWORKING}" = "no" ] && exit 6 /etc/rc3.d/S18rpcidmapd: [ "${NETWORKING}" != "yes" ] && exit 6 /etc/rc3.d/S19rpcgssd: [ "${NETWORKING}" != "yes" ] && exit 6 /etc/rc3.d/S57ntpdate: [ "$NETWORKING" = "no" ] && exit 1 /etc/rc3.d/S58ntpd: [ "$NETWORKING" = "no" ] && exit 1
We actually do that for ntp* services already (in network.py): log("\nStarting Network service") os.system("service network start &> /dev/null") os.system("service ntpdate start &> /dev/null") os.system("service ntpd start &> /dev/null")
Created attachment 527738 [details] Proposed patch
*** Bug 738120 has been marked as a duplicate of this bug. ***
Verified on 6.2-20111010.2: 1. before network setup, rpcbind & nfslock services are stopped. 2. then setup the network, rpcbind & nfslock services' are running. 3. register to rhevm and add nfs storage successfully. so set bug status to be verified.
Missed /etc/init.d/iscsid # if the network isn't up yet exit cleanly, NetworkManager will call us # again when the network is up [ ! -f /var/lock/subsys/network -a ! -f /var/lock/subsys/NetworkManager ] && exit 0
(In reply to comment #9) > Missed /etc/init.d/iscsid > > # if the network isn't up yet exit cleanly, NetworkManager will call us > # again when the network is up > [ ! -f /var/lock/subsys/network -a ! -f /var/lock/subsys/NetworkManager ] > && > exit 0 This is not really needed. vdsm runs iscsiadm which should start iscsi daemon as needed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1783.html