yum update breaks omsa?

[Michael E Brown]

On Thu, Apr 12, 2007 at 09:27:28AM -0400, Zembower, Kevin wrote:
> The update may not be broken. I get the same result with the omreport
> command, but needed the 'storage' option to get the output I expected:
> 
> www:~# omreport storage 
> 
> For further help, type the command followed by -?


Can you check your alertlog?
  # omreport system alertlog

I just noticed on my system, I got:

Severity      : Ok
ID            : 2164
Date and Time : Thu Apr 12 08:46:39 2007
Category      : Storage Service
Description   : See readme.txt for a list of validated controller driver versions.

Severity      : Non-Critical
ID            : 2131
Date and Time : Thu Apr 12 08:46:39 2007
Category      : Storage Service
Description   : The current firmware version  521S is older than the required firmware version 522A for a controller of model PERC 4e/Di:  Controller 0 (PERC 4e/Di) 

So, maybe it isnt giving information because the PERC firmware is too
old? I'll be updating my firmware and checking again soon.
--
Michael


> 
>  
> 
> www:~# omreport storage controller
> 
>  Controller  PERC 4e/Di (Embedded)
> 
>  
> 
> Controllers
> 
> ID                                : 0
> 
> Status                            : Ok
> 
> Name                              : PERC 4e/Di
> 
> Slot ID                           : Embedded
> 
> State                             : Ready
> 
> Firmware Version                  : 521S
> 
> Minimum Required Firmware Version : Not Applicable
> 
> Driver Version                    : Not Applicable
> 
> Minimum Required Driver Version   : Not Applicable
> 
> Number of Connectors              : 2
> 
> Rebuild Rate                      : 30%
> 
> BGI Rate                          : Not Applicable
> 
> Check Consistency Rate            : Not Applicable
> 
> Reconstruct Rate                  : Not Applicable
> 
> Alarm State                       : Not Applicable
> 
> Cluster Mode                      : Not Applicable
> 
> SCSI Initiator ID                 : 7
> 
> Cache Memory Size                 : 256 MB
> 
> Patrol Read Mode                  : Not Applicable
> 
> Patrol Read State                 : Not Applicable
> 
> Patrol Read Rate                  : Not Applicable
> 
> Patrol Read Iterations            : Not Applicable
> 
>  
> 
> www:~#
> 
>  
> 
> Hope this helps.
> 
>  
> 
> -Kevin
> 
> ________________________________
> 
> From: linux-poweredge-bounces at dell.com
> [mailto:linux-poweredge-bounces at dell.com] On Behalf Of Jeff Potter
> Sent: Thursday, April 12, 2007 8:38 AM
> To: linux-poweredge at dell.com
> Subject: yum update breaks omsa?
> 
>  
> 
>  
> 
> Hi List,
> 
>  
> 
> It looks like an update to OMSA last night has "broken" our monitor
> scripts that rely on omreport, which itself now returns nothing:
> 
>  
> 
> 	# omreport storage
> 
> 	For further help, type the command followed by -?
> 
> 	 
> 
> 	# 
> 
>  
> 
> I've tried a srvadmin-services.sh, just to see if that clean this up,
> but no go.
> 
>  
> 
> Thoughts?
> 
>  
> 
> Here's what yum.log shows as having been updated:
> 
>  
> 
>             Apr 12 04:23:15 Updated: srvadmin-omilcore.i386 5.2.0-460
> 
>             Apr 12 04:23:27 Updated: srvadmin-deng.i386 5.2.0-460
> 
>             Apr 12 04:23:27 Installed: srvadmin-omauth.i386
> 5.2.0-460.rhel4
> 
>             Apr 12 04:23:35 Updated: srvadmin-omacore.i386 5.2.0-460
> 
>             Apr 12 04:23:36 Updated: srvadmin-cm.i386 5.2.0-460
> 
>             Apr 12 04:23:36 Updated: srvadmin-odf.i386 5.2.0-460
> 
>             Apr 12 04:23:43 Updated: srvadmin-storage.i386 5.2.0-460
> 
>             Apr 12 04:23:43 Updated: srvadmin-ipmi.i386 5.2.0-460.rhel4
> 
>             Apr 12 04:23:48 Updated: srvadmin-hapi.i386 5.2.0-460
> 
>             Apr 12 04:23:48 Updated: srvadmin-isvc.i386 5.2.0-460
> 
>             Apr 12 04:23:52 Updated: srvadmin-omhip.i386 5.2.0-460
> 
>             Apr 12 04:23:52 Updated: srvadmin-storageservices.i386
> 5.2.0-460
> 
>             Apr 12 04:23:52 Updated: srvadmin-base.i386 5.2.0-460
> 
>  
> 
>  
> 
> best,
> 
> Jeff
> 
>  
> 
>  
> 
> P.S. I also noticed this output was generated in from yum.cron -- it
> would be nice if this didn't get sent out on automated updates.
> 
> 
> 
> 
> /etc/cron.daily/yum.cron:
> 
>  
> 
>      To start all installed services without a reboot,
> 
>      enter the following command:  srvadmin-services.sh  start
> 
>  
> 
> warning: /etc/pam.d/omauth saved as /etc/pam.d/omauth.rpmorig
> 
>  
> 

> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq