The configuration attribute smfRebootTimeout specifies node reboot time max timeout.
This reboot timeout is multiplied by other timout.
In method SmfUpgradeStep::nodeReboot(), function getNodeDestination() is called inside the node reboot timeout loop.
Function getNodeDestination() also contain an internal timeout. So the timeouts are multiplied.
Attached patch could be a potential fix, if the scope of the ticket is priarily to include the timespent in getNodeDestination().
patch
branch: opensaf-4.5.x
parent: 6478:431248e42a9e
user: Mathivanan N.P.mathi.naickan@oracle.com
date: Thu Apr 16 11:50:16 2015 +0530
summary: smfd: adjust smfRebootTimeout to include time spent in getNodeDestination [#1272]
changeset: 6482:2e9c417cca42
branch: opensaf-4.6.x
parent: 6479:43dcc23b0336
user: Mathivanan N.P.mathi.naickan@oracle.com
date: Thu Apr 16 11:50:16 2015 +0530
summary: smfd: adjust smfRebootTimeout to include time spent in getNodeDestination [#1272]
changeset: 6483:dff285e6e84a
tag: tip
parent: 6480:6fa5ee0bc4d4
user: Mathivanan N.P.mathi.naickan@oracle.com
date: Thu Apr 16 11:50:16 2015 +0530
summary: smfd: adjust smfRebootTimeout to include time spent in getNodeDestination [#1272]
Related
Tickets:
#1272