Ok I ended up splitting it into 4 separate tasks and it worked fine.  The total number of targets was 86.  Is that too many for a single task?

No, none of them showed NULL or no value for the current version.  I kept trying and eventually it worked as expected.

Hi,

100+ is definitely very high from OME part. What we support is 30 targets per task together. We would recommend, you create another set of system update tasks on next 30 servers once this task finishes because the load will be on the same task manager and the capability is supported for 30 devices together.

Hmm, I have had another task that ran against 65 targets without problems.

I did break up this one into smaller groups and it seemed to work, but then in another case it DIDN'T help... even though only 12 targets were selected.  The job is saved but never appears in the task execution window.  And when I double click the saved task it shows no targets.  Weird.  I'll try to figure out what triggers this issue but I'm not sure yet...

Hi Pupul - Is this 30 target ceiling listed in the OME manual?

Hi,

So for the 12 targets which you have selected, can you check if any of the components are showing the installed version as NULL.

You can check that from the system update page itself, navigate to the installed version column, click on the filter and check if anything is NULL or blank.

This is weird. But since it worked for you, i guess we can let it be and if it ever happens again, i would suggest you to enable task manager logs for OME. Those logs can help us figure out what is going wrong.

Hi Cameron,

It should be a part of the user guide or system update white paper, i will have to do some digging to check where exactly it is mentioned.

I'm still experiencing this problem.  I created a task to update the DRAC firmware on just one host.  I configured it to "run now".  The task shows up in the System Update Tasks pane, but never executes (doesn't show up in the Task Execution History pane).

Ok, thanks for the extra detail.

Often this is caused by the job queue being filled up on the DRAC.  Can you take a look at that using the iDRAC console or use the Dell Troubleshooting tool (installed on the OME desktop)?

Thanks,

Rob

delltechcennter.com/ome

The Troubleshooting tool seemed to be fine when I tested WSMAN/DRAC.

I'm not sure what I should be looking for if I log in to the DRAC directly.  Can you elaborate?

BTW - this was an out-of-band IDRAC fw upgrade attempt.  I tested it on a second server with the same results.  The job never seems to be executed.

There should be some job queue stuff hidden somewhere in that tool.  List/clear job queue, etc.

thx!

Ok, I see it now.  I had it list the jobs and it shows this:

DCIM_LifecycleJob
InstanceID = JID_CLEARALL
JobStartTime = TIME_NA
JobStatus = Pending
JobUntilTime = TIME_NA
Message =
Name = CLEARALL
PercentComplete =
MessageID =

I think the problem is with OME itself.  Maybe the engine that runs tasks stalls or something.  I ended up restarting the OME server and resubmitting the job to update the DRAC fw, and it appeared in the "Task Execution History" window right away like normal.

I'm not sure what that job was, but I went ahead and performed the "Delete All Jobs" action.  It claimed to be successful, but when I ask it to list jobs it still shows that same thing from above.