Hide Forgot
== Comment: #0 - SUBRATA MODAK <Subrata Modak <subrata.ibm.com>> - 2011.05.10 05:51:44 == ---Problem Description--- The following message is consistently produced during every system boot in RHEl5.7-Alpha: "Starting ibmvscsisd: /etc/ibmvscsis.conf file does not exist [FAILED]" The sequence is: " ... Starting hpiod: [ OK ] Starting hpssd: [ OK ] Starting ibmvscsisd: /etc/ibmvscsis.conf file does not exist. [FAILED] Starting iprdump: Starting ipr dump daemon[ OK ] ... " Regards-- Subrata Contact Information = Subrata Modak <subrata.modak.com>, Linda Xie <lxie.com> ---uname output--- Linux 2.6.18-259.el5 #1 SMP Fri Apr 29 01:11:49 EDT 2011 ppc64 ppc64 ppc64 GNU/Linux Machine Type = 8231-E2C-10708FP ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Mentioned Above ---Installation and Packaging Component Data--- Install disk info: N/A Install method: NIM Install ISO Information: RHEL5.7-Server-20110430.2-ppc-DVD.iso Userspace tool common name: ibmvscsid daemon The userspace tool has the following bit modes: N/A Userspace rpm: N/A Userspace tool obtained from project website: na == Comment: #2 - ARUNA H. BALAKRISHNAIAH <arunabal.com> - 2011.05.16 07:49:38 == Hi, There is no package providing /etc/ibmvscsis.conf and looks like the file is obsolete. In that case starting service would not be required. Thanks, Aruna.
------- Comment From Subrata Modak subrata.ibm.com 2011-05-17 04:46 EDT------- RH, Kindly let us know your thoughts on this. I believe this has been existing even in earlier RHEL5* release. So, may be we need to clean this.
------- Comment From lxie.com 2011-05-18 12:03 EDT------- Brian, Is /etc/ibmvscsis.conf needed? Linda
------- Comment From brking.com 2011-05-18 13:18 EDT------- (In reply to comment #7) > Brian, > > Is /etc/ibmvscsis.conf needed? No. In fact, there is no reason to start ibmvscsid on RHEL 5. That daemon is used to manage Virtual SCSI *Serving* as done by the ibmvscsis driver, which is not in RHEL 5 and is now deprecated.
------- Comment From Subrata Modak subrata.ibm.com 2011-05-24 06:12 EDT------- > > Brian, > > > > Is /etc/ibmvscsis.conf needed? > > No. In fact, there is no reason to start ibmvscsid on RHEL 5. That daemon is > used to manage Virtual SCSI *Serving* as done by the ibmvscsis driver, which is > not in RHEL 5 and is now deprecated. Hello RH, Can we remove this ? Regards-- Subrata
------- Comment From Subrata Modak subrata.ibm.com 2011-06-08 08:11 EDT------- RH, Please let us know your thoughts on this !! Regards-- Subrata
Changing platform to ppc64. Changing component to ppc64-utils, which owns ibmvscsisd. anaconda does nothing with this service script, it's all handled by the ppc64-utils package.
Created attachment 503891 [details] [PATCH] powerpc-utils: Do not install vscsi server tools/scripts ------- Comment on attachment From brking.com 2011-06-09 09:10 EDT------- This is probably the simplest way to resolve this bug. I recently sent a patch upstream to stop installing the vscsis init.d script. Upstream commit: http://powerpc-utils.git.sourceforge.net/git/gitweb.cgi?p=powerpc-utils/powerpc-utils;a=commitdiff;h=4f1d829e65bf240329f6130bf74c7eaa6fc3a8ab
------- Comment From brking.com 2011-06-09 14:27 EDT------- Since this is only a normal priority bug, and we are getting late in the 5.7 cycle, I suggest we defer this to 5.8. We plan to request a full powerpc-utils package refresh for 5.8, which will include the fix for this. Once the 5.8 feature is created, we can make this bug depend on it.
------- Comment From Subrata Modak subrata.ibm.com 2011-06-10 07:12 EDT------- Thanks Brian, Changing the Target Milestone accordingly. Regards-- Subrata
Verified on RHEL5.8-Server-20120105.0: kernel-2.6.18-303.el5 ppc64-utils-0.13-10.el5 /etc/init.d/ibmvscsisd startup script is not present and there's no error message during booting: Starting automount: [ OK ] [ OK ] Starting hpiod: [ OK ] Moving to VERIFIED.
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/RHEA-2012-0186.html