Resolution:
Description:
============
When upgrading TIBCO ActiveMatrix BPM (hotfix), an error occurs at the 'Reprovisioning all BPM Nodes' task stage.
The error looks as follows -
..
ERROR - Node Change features failed
ERROR - Change features node 'bpmnode' failed : TIBCO-AMX-HPA-000123: Provisioning features on the node BPMNode has failed with an error that can be usually recovered from, by retrying the same action using the resolve option provided for the action. Be aware, however, that the resolve option internally restarts the node and hence will momentarily disrupt all applications on this node. For this type of failure, it is unlikely the action will succeed without using the resolve option.
..


Environment:
===========
TIBCO ActiveMatrix BPM 1.1.1
TIBCO ActiveMatrix BPM 1.2.0
All platforms


Symptoms:
========
Review your upgrade logs and the 'Reprovisioning all BPM Nodes' section.

C:\Program Files\tibco\amx-bpm\bpm\1.2\scripts\upgrade

The section of the logs is as follows:
=================================================================
Task:   Reprovisioning all BPM Nodes
=================================================================

INFO - Initializing JSSE's crypto provider class com.sun.net.ssl.internal.ssl.P
rovider in default mode
INFO - Processing 1 objects
INFO - Reprovisioning Nodes...
INFO - Successfully start to reprovision Node 'BPMNode'
INFO - .
INFO - .
ERROR - Node Change features failed
ERROR - Change features node 'bpmnode' failed : TIBCO-AMX-HPA-000123: Provisioni
ng features on the node BPMNode has failed with an error that can be usually rec
overed from, by retrying the same action using the resolve option provided for t
he action. Be aware, however, that the resolve option internally restarts the no
de and hence will momentarily disrupt all applications on this node. For this ty
pe of failure, it is unlikely the action will succeed without using the resolve
option. Error code: 7., caused by: java.lang.Exception: TIBCO-AMX-HPA-000262: Th
e provisioning failed in stable mode because the set of components to remove was
not self-contained: at least one other component in the runtime is wired to one
or more components that are being removed.


Cause:
=====
Due to previous failed user application un-deployments, the last stage up upgrade, the reprovisioning of the BPMNode, will fail.


Resolution:
==========
In order to resolve this issue using the AMX Administrator, navigate to Infrastructure, Nodes then Features.

For a given user application feature that is 'Marked for Uninstall', locate the earliest version of it and then click 'Add', ensuring you pick the correct earlist version to add. Click Save, then Apply. This in turn will reprovision the BPMNode and change it's status from 'Out of Sync' to 'In Sync'.

i.e. ,
You have three Features called 'com.example.abcProj', that are 'Marked for Uninstall'
Locate the earlist version timestamp and 'Add' that same Feature again, selecting the timestamp associated with it.
Once done, click 'Apply'.

If it is the case that there are other user application features still 'Marked for Uninstall', then select each one in turn, find out the earliest timestamp and 'Add' this feature again. Click Apply and repeat for all Features that are 'Marked for Uninstall'.

Eventually, the BPMNode will be reprovisioned again and the status of the BPMNode will change to 'In Sync'.