Update stuck at 3%

Hello Kilobox,

The length of time it takes can depend on a lot of things like;

• is your management and production network traffic separated
• how many systems are updated
• how many updates are being applied
• some updates require the host to reboot, some more than once

Have you verified if the updates applied successfully?

Also I tried restarting the server for which the update-job was created. The task remained hanging at 3%. Perhaps this is a problem on the side of the OME itself, and it cannot download the packages to itself?

Hello

• traffic separated. Yes
• how many systems are updated. Only one
• how many updates are being applied. Any
• some updates require the host to reboot, some more than once. I know, i choose the appropriate option

Example:

Choose UpdatesSettingsStuck

Aaand that is all. The task stuck in "running" state.

Can you tell me what exactly is happening at this stage?

At the same time, some packages are installed normally.

As if OME can't access some of the packages?

Catalog updated:

Hi,

There might be a couple of reasons that the update could not proceed and it's stuck at processing. It's best that you can review the OME logs at Monitor tab, Audit logs. If there is no clue, you will need to access to the iDRAC of the target server and check the LC logs. It should let you know if an update has failed or any trace to what could be the reason. 

Some of the updates are able to be applied, so OME shouldn't be the root cause, but would rule out the possibility. Maybe some of the updates are too far apart between versions, which need a staged version update. Probably you might want to check it out which particular update has cause the verification stage to be stuck.

If else fails to find out, I would suggest to give the support a call for OME expert support to enable FSD debug and check further on what could be the cause.