- **status**: unassigned --> not-reproducible
- **Comment**:
The issue is not reproducible now. Attached is the AMFD trace which shows it
works fine. After locking the sponsor, tolerance timer is started. AMF is
removing the dependent after expiry of tolerance timer. Also si dep states of
all the dependents is updated to SPONSOR_UNASSIGNED.
---
** [tickets:#295] dependent SI is assigned when sponsor SI is locked in no
redundancy model**
**Status:** not-reproducible
**Milestone:** future
**Created:** Wed May 22, 2013 11:25 AM UTC by Nagendra Kumar
**Last Updated:** Wed May 22, 2013 11:25 AM UTC
**Owner:** nobody
Migrated from http://devel.opensaf.org/ticket/2572
Changeset : 3406
Model : Nored
Dependencies configured :
safDepend=safSi=SI1\,safApp=testNoRedApp,safSi=SI2,safApp=testNoRedApp (
tolerance 10 sec)
safDepend=safSi=SI1\,safApp=testNoRedApp,safSi=SI3,safApp=testNoRedApp
(tolerance 20 sec )
safDepend=safSi=SI2\,safApp=testNoRedApp,safSi=SI4,safApp=testNoRedApp (
tolerance 0 sec)
safDepend=safSi=SI3\,safApp=testNoRedApp,safSi=SI4,safApp=testNoRedpp (
tolerance 20 sec )
2 SU's are available in the cluster ( instantiated ) . 4 SI's are configured.
SU1 is assigned SI1 and SU2 is assigned SI2.
When SI1 is locked, SI3 is assigned active for SU1, which should not be done.
As the dependent cannot be given active callback when sponsor is unassigned.
List of notifications while processing admin lock of SI1 :
Mar 8 14:30:57 - Alarm¶
eventType = SA_NTF_ALARM_PROCESSING
notificationObject = "safSi=SI1,safApp=testNoRedApp"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.5 (0x5)
additionalText = "SI designated by safSi=SI1,safApp=testNoRedApp has no current
active assignments to any SU"
probableCause = SA_NTF_SOFTWARE_ERROR
perceivedSeverity = SA_NTF_SEVERITY_MAJOR
Mar 8 14:30:57 - State Change¶
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject = "safSu=SU2,safSg=SG,safApp=testNoRedApp"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.110 (0x6e)
additionalText = "The HA state of SI safSi=SI1,safApp=testNoRedApp assigned to
SU safSu=SU2,safSg=SG,safApp=testNoRedApp changed"
additionalInfo = "safSi=SI1,safApp=testNoRedApp"
sourceIndicator = SA_NTF_OBJECT_OPERATION
State ID = SA_AMF_HA_STATE
New State: SA_AMF_HA_QUIESCED
Mar 8 14:30:57 - State Change¶
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject = "safSi=SI1,safApp=testNoRedApp"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.104 (0x68)
additionalText = "Admin state of safSi=SI1,safApp=testNoRedApp changed"
sourceIndicator = SA_NTF_MANAGEMENT_OPERATION
State ID = SA_AMF_ADMIN_STATE
New State: SA_AMF_ADMIN_LOCKED
Mar 8 14:30:57 - State Change¶
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject = "safSi=SI3,safApp=testNoRedApp"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.111 (0x6f)
additionalText = "The Assignment state of SI safSi=SI3,safApp=testNoRedApp
changed"
sourceIndicator = SA_NTF_OBJECT_OPERATION
State ID = SA_AMF_ASSIGNMENT_STATE
New State: SA_AMF_ASSIGNMENT_FULLY_ASSIGNED
Mar 8 14:31:08 - Alarm¶
eventType = SA_NTF_ALARM_PROCESSING
notificationObject = "safSi=SI2,safApp=testNoRedApp"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.5 (0x5)
additionalText = "SI designated by safSi=SI2,safApp=testNoRedApp has no current
active assignments to any SU"
probableCause = SA_NTF_SOFTWARE_ERROR
perceivedSeverity = SA_NTF_SEVERITY_MAJOR
Mar 8 14:31:18 - Alarm¶
eventType = SA_NTF_ALARM_PROCESSING
notificationObject = "safSi=SI3,safApp=testNoRedApp"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.5 (0x5)
additionalText = "SI designated by safSi=SI3,safApp=testNoRedApp has no current
active assignments to any SU"
probableCause = SA_NTF_SOFTWARE_ERROR
perceivedSeverity = SA_NTF_SEVERITY_MAJOR
Changed 14 months ago by nagendra ¶
■milestone changed from 4.2.1 to future_releases
In no red model, handling for lock/failures are not there. We need to add all
these handlings. So, moving it into future releases.
---
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.
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
