OME to update OS Drivers Pack

I have had this exact same issue and with a completely clean deployment of 1.2

Thanks for your post.

OME should be able to support OS Driver Pack update. Are you getting any specific error?

If you want to ignore the update, you will be able to use Repository Manager tool to create custom catalog and exclude that update.

Here is the link for the white paper describing how to use Repository Manager with OME

http://en.community.dell.com/techcenter/extras/m/white_papers/20069223.aspx

Regards

Abhijit

The error is rather strange.  The update task shows 100% complete and successful.  But if you look at the details you see this:

Results:  

Downloading Packages.

Error Occured: Access is denied.  Check the following: Credentials entered are valid, iDRAC  is reachable from OME host and iDRAC is in a good state.

Software Update Task Failed.

But the idrac credentials are fine.  It can update every other application type, but the OS Drivers fail consistently across all our R720s and R710s.  

Is there any more detailed logging of the error anywhere?

Thanks for the info on the custom repository.  But if possible I'd rather fix this problem and use the standard Dell repository.

Yep, this is a clean 1.2 install as well.  Servers are ESXi 5.1 with OMSA 7.2. 

Can you tell me what version of iDrac firmware you have installed on the target server where you see this issue?

Typically they are all 1.37.35. One of the other issues I had posted was updating via iDRAC in general or our firmware would be 1.40.40.

en.community.dell.com/.../19520270.aspx

Mine are 1.40.40 and still having the problem.  

This is a known issue (inconsistent) with iDRAC firmware 1.30.30 onwards. Current plan is to release a patch, OME 1.2.1 soon to address this issue. We will post the details once it is made available.

ETA on that update???? To be honest this is a bit frustrating, how could this be a known issue with anything running firmware 1.30.30 and newer? Typically the r720's we receive out of the box are newer than that. This tells me your dev team never tested 1.2 against newer systems prior to release. This was working fine in 1.1.1 on the newest rev on a r720 the time 1.37.35.... This is disturbing as well since my test environment is now non-functional dues to having 1.2 installed and Dell Support is pushing us to upgrade our production OME server to 1.2 with these massive "Known" issues.

Hey Ron, yeah, understood.

I'll give you the latest info I have so I can be the most transparent.  At the moment we have root caused the issue, made the code fix,  have the patch created and it is in internal testing.  But for reasons you point out, we're trying to ensure we cover all the needed test cases.  We are also looking to characterize why this defect exists.  We'll try to provide as much info as we can in the readme file that comes along with the patch.    

As we've looked into it, we've noticed that it impacts 1.1.1 as well (even with 1.37), so it's possible that there are certain conditions in which the defect may impact some users but not others (e.g., a certain fw upgrade path?).  Again, we'll try to add useful detail to the readme that will help characterize impacted users.

I don't want to promise a date, but I would say the team is working hard to get this available for general download in two weeks or so.

Thanks for your patience.

Rob

I have escalated this within our normal Dell support team as waiting "2 weeks or so" is ridiculous. I have a clean install on v1.2 after I was told that it would be best to wipe and reload since my server was originally 1.0 then 1.1.1 and a few patches and the amount of issues I had after the v1.2 upgrade. I now have a brand new OME server (and SQL 2008r2 server) running v1.2 and I can not deploy anything, as 90% of my servers are r7xx, M7xx, M8xx series servers with greater than 1.35.35 firmware.

This is truly a shame..... I have been using OME prior to the 1.0 production deployment and have found it a very valuable tool in my work. With this 1.2 release this has completely crippled my support work and thinking about wiping and reloading 1.1.1 at this point is aggravating.

Hi Ron,

The issue will be with iDrac firmware 1.40.40 onwards. Going back to 1.1.1 will not fix it. The issue is how the firmware treats the update command.

If your iDracs are not at 1.40.40, you will be able to send the updates. As a work around till the patch is available, you can send all the other updates first before updating iDrac firmware. As Rob mentioned we are in the final test phase of the patch and we are trying to release it as early as possible.

Regards

Abhijit

And as an additional note to show the issue is specific to 1.2, I added one of my existing servers from this 1.2 test environment that we can not deploy to, on to our production OME server running 1.1.1 and we were then able to deploy the LifeCycle Controller application upgrade from 1.1.1.18 to 1.1.5.165 and the iDRAC firmware upgrade from 1.37.35 to 1.40.40.

That is NOT correct...

I can not send updates to any server via iDRAC and the firmware revisions are not 1.40.40, most are running 1.37.35 and some still on 1.35.35, we actually only have 1 server running 1.40.40 because we upgraded it manually to test. We have not been able to deploy any updates to a single server via iDRAC since we installed 1.2, both when we upgraded our legacy 1.1.1 environment and now with a completely clean, from scratch 1.2 environment. We were able to deploy to our iDRACs prior to upgrading to v1.2 and they were at the time still running either 1.37.35 or 1.35.35.

An example... If we try and deploy the LifeCycle Controller application upgrade from 1.1.1.18 to 1.1.5.165, which is an available update, it fails with the same error as I had posted in my other forum post..

"The task has failed because the device selected as a target does not support this type of task. For a detailed reference of what tasks can be run against specific devices and discovery methods, Refer to the Managing Remote Tasks section in the user guide. Also check if Dell OpenManage BMC Utilities are installed."