Start a Conversation

Solved!

Go to Solution

3449

June 22nd, 2021 06:00

update openmanage 3.6.1.6

I updated Openmanage Enterprise to 3.6.1 and after the reboot the Devices = 0.  Is there a way to recover them or does this require discovery again?

June 23rd, 2021 09:00

@stellr 

This could be an issue with Cache, Could you please clear the browser cache and update the browser version as well and let us know if you still experiencing this issue with devices lost.

Thanks,

Anil Kumar V K R

#I Work 4 Dell.

1 Rookie

 • 

116 Posts

June 22nd, 2021 08:00

If I could piggy-back on this post, are there any release notes available for this version (3.6.1.6)?

Could this be a known issue?

25 Posts

June 22nd, 2021 09:00

I have a feeling they overwrote the cached credentials of the inventory job.

 "Recommended actions: Make sure the credentials associated with the device management endpoint are valid and retry the operation."

I'm not exactly sure how to edit the job to give it the correct username/pw.  I have a case open with Dell for their benefit.   I hope it is helpful to somebody with future upgrades.

I don't know where the release notes are.  Google search doesn't seem to find them

25 Posts

June 22nd, 2021 10:00

Oh, you have to put a check mark next to the job in order to get the edit function.   I did that and the job ran, but still Devices=0.

2 Posts

June 22nd, 2021 10:00

I am having issues with this update. I have about 20 devices before the update, after updating i have 0. Also not able to discover these same devices anymore. I reverted back to my snapshot and will not be applying the update again until they confirm this is addressed and fixed.

25 Posts

June 22nd, 2021 10:00

you see on the right it knows the device, but not on the left, or in the device list.

 

Screenshot from 2021-06-22 13-15-23.png

June 22nd, 2021 11:00

We just upgraded to 3.6.1.6, and right after the OME appliance comes up, I tried to deploy a firmware update to a 13th Gen server, and the job just sits at 0% for more than 10 minutes with nothing appearing in the Execution Details of the job.  I also tried adjusting the warranty settings to hide the initial warranties and I get an "An unknown error has occurred.  Please try again." error message.  So it looks like this version of OME is just as bad as 3.6.0.  I'm going to revert to 3.5.0.

Moderator

 • 

3.7K Posts

June 22nd, 2021 11:00

Hello,

 

Thank you both for your report. I have an escalation into the Systems Management team to check on this.

 

stellr do you have a snapshot you could roll back to link jbeitler did?

 

Moderator

 • 

3.7K Posts

June 22nd, 2021 12:00

Could you let me know the type of Devices and the protocol used to discover?

 

It was also advised if anyone could call into support (1-800-945-3355 US/Canada) and set up a formal support case it could help progress this.  If you do please private message me the case number I can provide to my System Management engineer.

25 Posts

June 22nd, 2021 13:00

I do have a snapshot.  However, I didn't want to destroy this broken guy if it will help the debug process.  

25 Posts

June 22nd, 2021 13:00

Case#:<Moderator removed> Tag:<Moderator removed> R740XD

25 Posts

June 22nd, 2021 13:00

I did that this morning:   Case#: <Moderator removed> Tag: <Moderator removed> R740XD

Moderator

 • 

3.7K Posts

June 22nd, 2021 13:00

Would you be in a position you could call in and set up a formal support case?

Moderator

 • 

3.7K Posts

June 22nd, 2021 13:00

Thank you stellr. I have the numbers now and will forward.

Can you now delete the post with your case and service tag numbers? or I can edit for you. We don't want personal identifiable information posted on the web. 

No Events found!

Top