cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 
cancel
2467
Views
2
Helpful
4
Replies

ISE 2.2 Patch 3 install pending

randomuser
Level 1
Level 1

Hello together,

actually I try to install Patch 3 on ISE 2.2 virtual Appliance over WebUI. The installation is now running for about 3 hours. Anyone already installed Patch 3 successful?

The Output from 'show logging application patch.log tail' only show:

Tue Sep  5 14:11:44 MEST 2017

CPMPatchUtil: Creating Repo tmplocalpatchinstallrepo

stty: standard input: Inappropriate ioctl for device

and show 'logging application patchlogs/patchinstallmessage3' or 'show logging  application patchlogs/patchinstallstatus3' states only: Install in Progress

When trying to reload or stop the application manually I got the warning that APP_PATCH is running (i.e.: WARNING: An install/upgrade/remove is currently in progress! Continue with reload? (yes/no) [no] ?)

Thanks in advance.

4 Replies 4

gbekmezi-DD
Level 5
Level 5

Yes, installed without an issue in a 2 node virtual deployment.

randomuser
Level 1
Level 1

We decided to wait until today, but the Admin Node stated installation in progress. Then we decided to reload the virtual Appliance. The Appliance reloaded twice and Patch 3 was then successful installed.

Seems that the automatic reload was not performed. Then we installed Patch 3 through cli on all (5 more) Nodes, because the Patch was indeed uploaded through the WebUI Patch Installation to the other Nodes but the 'patch.log' showed failure when trying to install. Now everything runs fine.

Is there some known issue?  Or someone has the same experience on that?

Were you by chance using a self-signed certificate? Also, did you have forward and reverse DNS records in place?

I ran into an issue where installing 2.2 Patch 3 from the Web UI with a non-trusted certificate failed due to some kind of SSL error. Then, I attempted to install from the CLI, and it failed due to DNS resolution failing.  (These nodes were being installed new, thus the customer had not yet created the DNS records or provided the CA-signed ceritficates).

Please engage Cisco TAC to investigate it further.