I think, the discussion got deviated by the usage of PL string in nodes.cfg.
On the fist node in the opensaf cluster, the following info is filled up in
opensaf cfg files.
cat /usr/share/opensaf/immxml/nodes.cfg
SC node-1 node-1
SC node-2 node-2
PL node-3 node-3
PL node-4 node-4
PL node-5 node-5
PL node-6 node-6
cat /etc/opensaf/slot_id
1
cat /etc/opensaf/node_name
node-3
cat /etc/opensaf/node_type
controller
-> Opensafd starts successfully, but with the following output
safSISU=safSu=node-3\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
-> After a timegap of 5 minutes, the node went for reboot with the following
output.
Nov 1 12:31:22 CONTROLLER-1 osaffmd[3945]: Rebooting OpenSAF NodeId = 0 EE
Name = No EE Mapped, Reason: Activation timer supervision expired: no ACTIVE
assignment received within the time limit, OwnNodeId = 131343, SupervisionTime
= 60
Nov 1 12:31:22 CONTROLLER-1 opensaf_reboot: Rebooting local node; timeout=60
Observed behavior :
If user mistakenly populates the node_name with the payload's node_name and
starts the opensafd script, then user shall not be informed about
mis-configuration. The node reboots continuously as opensafd is enabled in
runtime by default during RPM installation.
Expected behavior :
Either fms / imm / amf should detect that the node_name used in bringing up
is intended for payload, but not for controller. More importantly, the node
should not go for reboot.
---
** [tickets:#2052] immtools: SC/PL field in nodes.cfg is not used**
**Status:** unassigned
**Milestone:** 5.0.2
**Created:** Tue Sep 20, 2016 09:41 AM UTC by Ritu Raj
**Last Updated:** Tue Sep 20, 2016 05:49 PM UTC
**Owner:** nobody
# Environment details
OS : Suse 64bit
Changeset : 7997 ( 5.1.FC)
# Summary
Controller able to join with invalid node_name
# Steps followed & Observed behaviour
1. Mistakenly configured controller node_name with PL-3 and the remaining
configuration files are properly installed and updated apart from
/etc/opensaf/node_name.
2. Bringup OpenSAF, OpneSAF still able to comeup with misconfigured node_name
Opensaf status:
fos1:/opt/goahead/tetware/opensaffire/suites/avsv/api/suites #
/etc/init.d/opensafd status
safSISU=safSu=PL-3\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
# Expected
OpenSAF should come up with only SC-1 / SC-2, as immxml generated with :
./immxml-clustersize -s 2 -p 2
./immxml-configure
---
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.------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
