#906 smfd: campaign can not be committed after cluster reboot in state completed

[Ingvar Bergström]

A cluster reboot in state "execution completed" will put the upgrade campaign in a fail state if the old unused versioned types are removed in the campaign wrapup "campCompleteAction" portion of the campaign.

This is because smfd always check if the versioned types specified in the campaign "targetEntityTemplate/type" portion exists in the system when starting up the procedure threads (after the cluster reboot).

If removed in the "campCompleteAction", the versioned types will be removed from the system before the campaign enters "execution completed" state.

When the campaign is in fail state it is impossible to commit the campaign.

Solution: modification info shall not be added for procedures in completed state.

[Ingvar Bergström]

changeset: 5278:985f1fff70f9
tag: tip
parent: 5275:01c884eda57e
user: Ingvar Bergstrom ingvar.bergstrom@ericsson.com
date: Wed May 14 14:28:10 2014 +0200
summary: smfd: campaign can be committed after cluster reboot in state completed [#906]

changeset: 5277:1768d48c1c6a
branch: opensaf-4.4.x
parent: 5268:9f5b74e50e3a
user: Ingvar Bergstrom ingvar.bergstrom@ericsson.com
date: Wed May 14 14:28:10 2014 +0200
summary: smfd: campaign can be committed after cluster reboot in state completed [#906]

changeset: 5276:422a57501142
branch: opensaf-4.3.x
parent: 5270:d7ac5a719f0d
user: Ingvar Bergstrom ingvar.bergstrom@ericsson.com
date: Mon May 19 08:51:17 2014 +0200
summary: smfd: campaign can be committed after cluster reboot in state completed [#906]