Cisco Prime Infrasturcture 3.0 to 3.1 Upgrade failing ... "% Pre-install step failed"

[keanej]

I have updated from 2.2 to 3.0, Did a backup of 2.2. built 3.0 on a fresh VM and restored backup .. all good. 

Now at 3.0

Now attempting to upgrade the 3.0 to 3.1.0.0.132 and alas no joy.

I have copied the tar.gz file to the defaultRepo on the VM to simply things. 

This how far the upgrade gets before bombing out...

Any help appreciated !!

CiscoPrime/admin# show version

Cisco Application Deployment Engine OS Release: 2.3
ADE-OS Build Version: 2.3.0.101-root
ADE-OS System Architecture: x86_64

Copyright (c) 2005-2010 by Cisco Systems, Inc.
All rights reserved.

Version information of installed applications
---------------------------------------------

Cisco Prime Infrastructure
********************************************************
Version : 3.0.0
Build : 3.0.0.0.78
Prime Add-Ons:
Prime Insight Agent ( 1.0.0 )
IVH-CiscoPrime-01/admin#

CiscoPrime/admin# dir disk:defaultRepo

Directory of disk:defaultRepo
9195620298 Dec 01 2016 10:32:46 XXXXXXXXX2__VER3.0.0.0.78_BKSZ175G_CPU8_MEM4G_RAM15G_SWAP15G_APPXXXXXXX.tar.gpg
3897967336 Dec 01 2016 10:58:05 PI-Upgrade-3.0.X_to_3.1.0.0.132.tar.gz
163507336 Dec 01 2016 13:43:22 pi303-10.ubf
45337021 Dec 01 2016 13:42:56 pi303_update_04-1.0.12.ubf

Usage for disk: filesystem
13508382720 bytes total used
74195144704 bytes free
92472696832 bytes available

CiscoPrime/admin# application upgrade PI-Upgrade-3.0.X_to_3.1.0.0.132.tar.gz defaultRepo
Save the current ADE-OS running configuration? (yes/no) [yes] ? no

Please ensure you have a backup of the system before proceeding.
Proceed with the application upgrade ? (yes/no) [yes] ?

DO NOT press ^C while the upgrade is in progress
Aborting upgrade with a ^C may leave the system in a unrecoverable state

Initiating Application Upgrade...
Stage 1 of 7: Transferring file ...
-- complete.
Stage 2 of 7: Unpacking file ...
-- complete.
Stage 3 of 7: Executing pre-install ...

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
System will reboot a few times to complete the upgrade process.
Please monitor the upgrade progress from the system console.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

ERROR : Please run the application upgrade from the system console to
monitor upgrade progress. Use system monitor, serial terminal or a virtual console
to initiate the upgrade.

WARNING : It is strongly recommended to copy the latest backups to an
external repository before proceeding with the upgrade.

% Pre-install step failed. Please check the logs for more details.

[Marvin Rhoads · Accepted solution]

Are you running the upgrade from the console in Vsphere / Vcenter as required?

An ssh console session will cause the failure you are seeing.

[Dmitri Olchevski]

That was the issue with my upgrade. I restarted it from the VM console and it is working now.

Thanks for the quick reply!

[keanej]

The actual error was a space issue on the defaultRepo

The syntax of deleting files from there is

del disk:/defaultRepo/MYFILESARETAKINGUPSPACE.tar.gz

to check all files are deleted, with the exception of your upgrade file

dir disk:/defaultRepo

The only file should be the upgrade file.

by using the SSH client, you don't see what the upgrade fault is, so all this needs to be done from the Console session on VMWare VSphere Client, which can be a pain as copy and paste dont work.

So using the Console session is the correct answer - thanks Marvin.