installation of cop file stuck in "Upgrade status: Installing" and cannot be canceled.

[themizzz21]

Hello,

CUCM cluster 12.5.1 SU4.

Upgrading the pub and sub nodes using the ciscocm.V12-5-1SU4_CSCvx83448_secure-ldap-fix_C0112.cop file, the whole procedure stuck in "Upgrade status: Installing".

The upgrade was done via GUI.

The procedure cannot be canceled using the utils system upgrade cancel command and the system returns the

"Installation of a Cisco Options Package (COP) cannot be canceled" message.

Servers were rebooted with the same result.

Installation file ends with the following message:

COP file installation completed successfully.

A reboot is NOT required.

#####################################################################################
[21/07/15_13:32:42] locale_install.sh: Not running installdb.
[21/07/15_13:32:42] locale_install.sh: failed to update the upgrade status in /common/log/install/upgrade_status.xml file
[21/07/15_13:32:42] locale_install.sh: Successful running of copstart for ciscocm.V12-5-1SU4_CSCvx83448_secure-ldap-fix_C0112.cop
[21/07/15_13:32:42] locale_install.sh: copy ciscocm.V12-5-1SU4_CSCvx83448_secure-ldap-fix_C0112.cop to /var/log/active/installed_options/

end of the file reached

Any idea of what to do?

Thank you very much.

[Rajan]

Hi,

Please login to CUCM command line and check "show version active" to see whether its showing this COP file. If not, you need to reinstall.

HTH
Rajan
Please rate all useful posts by clicking the star below and mark solutions as accepted wherever applicable

[themizzz21]

Hello, thank you for your reply,

admin:show version active
Active Master Version: 12.5.1.14900-63
Active Version Installed Software Options:
ciscocm.V12-5-1SU4_CSCvx83448_secure-ldap-fix_C0112.cop
cm-locale-combined_network-12.5.1.4001-1.cop
cm-locale-el_GR-12.5.1.4000-1.cop
ciscocm.V12.5.1SU4_CSCvx74275_em-headset_C0111-1.cop
admin:

I cannot cancel the installation procedure:

admin:utils system upgrade cancel
Canceling the upgrade. Please wait...

Installation of a Cisco Options Package (COP) cannot be canceled.

Upgrade status: Installing
Upgrade file: ciscocm.V12-5-1SU4_CSCvx83448_secure-ldap-fix_C0112.cop
Upgrade log: install_log_2021-07-15.13.16.41.log

Thank you.

[Jaime Valencia · Accepted solution]

I suggest you open a TAC to have this looked at, the reboot should have stopped any installation.

[themizzz21]

Apparently, i will go this way.

I think that the problem is the following:

[21/07/15_13:32:42] locale_install.sh: failed to update the upgrade status in /common/log/install/upgrade_status.xml file.

The system thinks that the installation is still on going.

Thank you.

[Nithin Eluvathingal]

i have installed this cop for couple of my customer and that was through cli.

Better to reach out TAC.

It’s clearly mentioned that you should use this cop through cli.

COP file to fix CSCvx83448 in 12.5.1SU4. The COP file must be installed via the CLI.

This COP file should only be installed via the CLI, installing via the GUI will result in the fix not being correctly applied until the server is rebooted. It should be installed on all nodes in the cluster, starting with the Publisher.
A reboot is not required as part of the COP file install (unless the COP file is installed via the GUI as noted above).

[themizzz21]

Hello and thank you for the reply,
Yes, i saw this after the incident.
Nevertheless it states that "installing via the GUI will result in the fix not being correctly applied until the server is rebooted".
The server was rebooted but the result was the same.
I think that the same issue could arise even if the procedure performed from within the CLI.

[Nithin Eluvathingal · Accepted solution]

Better contact   TAC.

note:- Before installing, go through the readme files.

[lior look]

it happened to me in 12.5 SU5

I met this issue after installation cop file for bug fixing, so this issue presents in any cop file.

I tried couple things to solve that with no success like

cucm rebooting, cucm shutdown

utile system upgrade cancel

I also tried to switch version twice but nothing helped to fix that.

so I took a DRS backup and I made switch version, then I started to upgrade the system to SU5 again + restore from DRS.

the issue disappeared