---
** [tickets:#893] smfd: node destination not found in cluster reboot step**
**Status:** assigned
**Milestone:** 4.5.FC
**Created:** Fri May 09, 2014 04:51 AM UTC by Ingvar Bergström
**Last Updated:** Fri May 09, 2014 04:51 AM UTC
**Owner:** Ingvar Bergström
In a cluster reboot step, directly after the step resumes after the reboot: SMF
continues the step execution and try to offlineInstall new bundles which does
not require reboot to install.
The installation command can be directed to any node in the cluster depending
on what is specified in the upgrade campaign.
If the controller which resumes the campaign execution reboot faster than the
node addressed to install the new bundle, the node destination is not found at
once and the installation fails.
The solution is to make smfd to wait for the node destination to appear. If the
node destination does not appear within a timeout period the campaign will
fail. The proposal is to use the configurable node reboot timeout for this
purpose as well.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
