Isilon: Patch status shows as AdHoc

mycluster-3#   isi upgrade patches list

Patch Name   Description                                           Status
--------------------------------------------------------------------------
patch-248568 [8.1.2.0 UGA-RUP 2019-04] Multiple Userspace Fixes... AdHoc 
patch-248570 [8.1.2.0 KGA-RUP 2019-04] Multiple Kernel/Reboot R... AdHoc 
--------------------------------------------------------------------------

The status of the patch should be seen as Installed.

An upgrade rollback occurred and failed to complete.

The adhoc status means that the patch is installed on some (or even all) nodes but not registered to the cluster. This usually happens when a patch was installed with the isi_patch utility but was never installed with the "isi upgrade patches" command.

Using the command "isi upgrade patches view <patch>" will show a list of node id's where the patch is installed. Example abbreviated output is shown:

mycluster-3# isi upgrade patches view patch-248568
 Patch Name: patch-248568
 Description: [8.1.2.0 UGA-RUP 2019-04] Multiple Userspace Fixes (April 2019)
      Status: AdHoc
       Nodes: 2, 3, 4, 5, 6

To get the patch to a normal "Installed" status, simply install the patch again with the normal "isi upgrade patches install" command. For nodes where the patch is actually already installed, this will register the patch; for nodes where the patch is missing, this will install the patch.

If the patch is actually listed as installed on all nodes, executing the "isi upgrade patches install" command will simply clean up the cluster patch register. No outage or actual patch install activity is occurring because the node will be skipped if "isi upgrade patches view" shows the patch on the node. If the patch is listed as installed on ALL nodes using the "view" command, the cluster patch registry is cleaned-up and corrected when the install command is executed.

For any node where the patch is NOT installed, however, execution of the command will install the patch, with the consequences of the patch install (service restart or node reboot). If in doubt, execute the command in an offline window.

After the execution of the command - as shown in the example above - the following is seen:
mycluster-3# isi upgrade patches install patch-248568

mycluster-3# isi upgrade patches list

Patch Name   Description                                           Status   
----------------------------------------------------------------------------
patch-248568 [8.1.2.0 UGA-RUP 2019-04] Multiple Userspace Fixes... Installed
patch-248570 [8.1.2.0 KGA-RUP 2019-04] Multiple Kernel/Reboot R... AdHoc    
----------------------------------------------------------------------------
Total: 2