changeset: 4980:25049badceee
branch: opensaf-4.2.x
parent: 4976:a3eac1e94d1d
user: Nagendra Kumar<nagendr...@oracle.com>
date: Tue Feb 18 12:28:14 2014 +0530
summary: amf: set comp oper state to enable when corresponding node is
present [#324]
changeset: 4981:4923264e3e0f
branch: opensaf-4.3.x
parent: 4977:af531011631c
user: Nagendra Kumar<nagendr...@oracle.com>
date: Tue Feb 18 12:28:49 2014 +0530
summary: amf: set comp oper state to enable when corresponding node is
present [#324]
changeset: 4982:591659c36425
branch: opensaf-4.4.x
parent: 4978:7698cc450ac1
user: Nagendra Kumar<nagendr...@oracle.com>
date: Tue Feb 18 12:38:18 2014 +0530
summary: amf: set comp oper state to enable when corresponding node is
present [#324]
changeset: 4983:f98f7c58bd58
tag: tip
parent: 4979:44d6f28f8b15
user: Nagendra Kumar<nagendr...@oracle.com>
date: Tue Feb 18 12:38:34 2014 +0530
summary: amf: set comp oper state to enable when corresponding node is
present [#324]
[staging:25049b]
[staging:492326]
[staging:591659]
[staging:f98f7c]
---
** [tickets:#324] amf: The operational state of a component stays DISABLED
while that of SU gets ENABLED when the respective node gets added into the
cluster.**
**Status:** fixed
**Created:** Fri May 24, 2013 09:19 AM UTC by Praveen
**Last Updated:** Thu Jan 23, 2014 06:23 AM UTC
**Owner:** Nagendra Kumar
Migrated from http://devel.opensaf.org/ticket/2199.
OS: SLES11 32bit
Platform: VirtualBox?
Changeset: 2852
Opensaf is running successfully on two nodes, SC-1, SC-2.
PL-3 is configured by opensafd is not running on this node.
Configuration:
SG in 2N model, with
3 SUs, one on each node, having one component each
1 SI having one CSI
The configuration is added runtime with SUs in LOCKED_INSTANTIATION presence
state.
This is issue can be reproduced in two ways:
1.Adding a new SU runtime on an existing node
SU1 and SU2 are added on the SC-1 and SC-2 respectively and their operational
states are set to ENABLED. But the components have the DISABLED operational
state.
2.Adding a new SU runtimg on a non-existing node and adding the node to the
cluster
SU3 gets added to the AMF configuration with DISBALED operational state as PL-3
is down. When opensafd is brought up on PL-3, SU3 becomes ENABLED but its
component remains DISABLED.
Changed 18 months ago by pavan
When ADMIN LOCK-IN is performed on an SU (which is enabled and all its
components are also enabled), all the components are being moved to DISABLED
operational state.
Hope this issue is related to the above reported ticket. So updating the same.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
