The local or downloaded package couldn't be validated: Invalid Package

I have the same issue.
OME console was updated to all the way from 3.5 to 3.8 yesterday.  Turned out to be a coincidence: I rolled the console back to 3.5 from backups and got the same "The local or downloaded package couldn't be validated. Invalid Package." message when I attempted a firmware update.

I suspect something might be broken on Dell's side.

So things just started working again, both the 3.5 and 3.8 versions of the console can now validate the downloaded packages.  Whatever was going on with the source servers seems to have been corrected, at least for me.  How does it go on your end Nexus ?

If update directly via the iDRAC with the same package it works OK, but I have over 100 servers to do, so not keen on doing that.

If the file that is on the appliance is corrupt would be good if there was a way delete it from the internal appliance, dont currently know what to do to fix it.

The more I use OME, the more it feels like a half finished product.

I had the same issue. i rebooted the appliance. After that this issue is fiexed.

Still doing the same, I will try again on Monday

Having the same issue, rebooting the appliance did not help. On console version 3.8.4.

Still having same issue and appears to be issue on all our servers. Restarting appliance did not solve the problem. Anyone know the route cuase of what this is?

In the release notes I noticed this:

CIFS V2 need to be reset post upgrade as it automatically switches to CIFS V1. You
must restore the Built-in Appliance Share setting back to CIFS V2, on the Console
Preferences page ( Application Settings > Console Preferences) even if the UI
continues to display CIFS V2 as the preference.

So i changed it back to CIFS v1 clicked Apply then changed it back to CIFS v2 and clicked Apply. The updates now seem to be working. Argghh Dell, not impressed.

Hey!

Guess not - I have opened a service request at Dell. This was the first response I've got today:

"This could be an issue with the load balancer servers for the dl.dell.com replicas. Engineering is already flagged about this & should be working with IT on this."

Tried out the CIFS-swap, doesn't work for us.

BR

Guenther

Hey...it worked for me if you change to CIFSv1, reboot and after reboot change back to CIFSv2.

Regards

Hi!
Same error here, restarted the appliance and also tested the CIFS-swap: Still doesn't work (Version 3.8.2).


Wolfgang

Hi,

nope cannot confirm it. Changed to CIFSv1, rebooted the appliance, changed back to CIFSv2. Doesn't work.

BR

Guenther

Would you do me a favor and confirm a couple things for me?

Is this only occurring when trying to update with the idrac package, or does it also occur on something like the BIOS update package as well?

If so, does it occur on any of the even smaller package updates?

Lastly, would you please private message me the svc tag for the system, in case I need to submit this?

Let me know.

Hi Chris,

yeah, I've got this

"This could be an issue with the load balancer servers for the  replicas. Engineering is already flagged about this & should be working with IT on this."

I've escalated this today because we cannot deploy new servers for a project  

BR

Guenther

Hi Chris,

it occours if I try to update the whole server including iDrac, Firmware etc. Worked fine for

me in the past (last tried it two month ago...). I have opened a case with dell do you need

the service request id?

BR

Guenther