cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
785
Views
0
Helpful
6
Replies

CUCM 8.6.2 to 9.1.2 Upgrade fails

Richard Simmons
Level 3
Level 3

I am trying to complete an upgrade of CUCM 8.6.2 to 9.1.2 however the upgrade fails at the very end - I have attempted this 4 times in various different ways from using SFTP to local media I get the following error;

 

HWModel=7835I3
CPUCount=1
CPUType= Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz
CPUSpeed=2000
MEMSize=4096
BIOSVer=IBMCorp. -[D6E150CUS-1.11]- 02/08/2011
ObjectId=1.3.6.1.4.1.9.1.585
OSVersion=UCOS 5.0.0.0-2
SerialNumber= ********
VendorOID=1.3.6.1.4.1.2]|<LVL::Info>
05/17/2014 13:54:49 upgrade_install.sh|Cleaning up download...|<LVL::Info>
05/17/2014 13:54:49 upgrade_install.sh|Cleanup upgrade source area.|<LVL::Info>
05/17/2014 13:54:49 upgrade_install.sh|Ejecting DVD (/dev/sda1)|<LVL::Debug>
05/17/2014 13:54:51 upgrade_install.sh|Removing /common/download/9.1.2.10000-28>
05/17/2014 13:54:51 upgrade_install.sh|Started auditd...|<LVL::Info>
05/17/2014 13:54:52 upgrade_install.sh|Started setroubleshoot...|<LVL::Info>
05/17/2014 13:54:52 upgrade_install.sh|Changed selinux mode to enforcing|<LVL::>
05/17/2014 13:54:52 upgrade_install.sh|Cleaning up rpm_archive...|<LVL::Info>
05/17/2014 13:54:52 upgrade_install.sh|Removing /common/rpm-archive/9.1.2.10000>
05/17/2014 13:55:02 upgrade_install.sh|File:/usr/local/bin/base_scripts/upgrade>
05/17/2014 13:55:02 upgrade_install.sh|set_upgrade_result: set to 1|<LVL::Debug>
05/17/2014 13:55:02 upgrade_install.sh|is_upgrade_lock_available: Upgrade lock >
05/17/2014 13:55:02 upgrade_install.sh|is_upgrade_in_progress: Already locked b>
05/17/2014 13:55:02 upgrade_install.sh|release_upgrade_lock: Releasing lock (pi>

Installation of UCSInstall_UCOS_9.1.2.10000-28.sgn.iso failed

An unknown error occurred while accessing the upgrade file.

A system reboot is required when the upgrade process completes or is canceled. .

 

I have previously used this ISO for other clients without an issue and have checked the MD5 is correct

Has anyone else experienced this issue?

Thanks,

Richard

6 Replies 6

Manish Gogna
Cisco Employee
Cisco Employee

Hi Richard,

Please try the following steps.

Reboot Publisher

Set SELinux to permissive mode by using the command 'utils os secure permissive' on Publisher CLI.

Try the upgrade again.

Let us know if it helps.

Manish

Hi Manish,

thanks for getting back to me, we will need to arrange downtime to try this upgrade again - Is this a known bug, is there any documentation you have around this? 

Thanks,

Richard

Hi Richard,

Not exactly a bug, but i have seen similar cases where this solution worked.

Manish

Hi Manish,

We have tried the upgrade again having used the commands you have suggested and we still get the same error.

Regards,

Richard

We have got this resolved, after raising a case with TAC they identified that we were hitting the following bug;

CSCub53409

The detail on the bug is very limited but in our case it was caused by an issue with the numbering plan, GBNB 1.1(21) - we upgraded to the latest version 1.1(29) and the upgrade has now completed.

Hi Richard,

Thanks for updating the forum with the resolution, might help someone in the future.

Manish