- **status**: accepted --> not-reproducible
- **Part**: - --> d
- **Milestone**: 4.4.2 --> never
- **Comment**:
This issue is not reproducible. In Nored model, all three SIs are getting
assigned to different three SUs. Since all SIs are assigned, AMF rejects
dynamic creation of SI Dependency if SI is assigned:
immcfg -c SaAmfSIDependency
"safDepend=safSi=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1"
error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21)
OI reports: SI dep validation: adding dependency from existing SI
'safSi=AmfDemo,safApp=AmfDemo1' to SI 'safSi=AmfDemo1,safApp=AmfDemo1' is not
allowed
428.gz contains configuration and AMF traces after validation.
---
** [tickets:#428] NO Redundancy model allows si-si dependency creation having
SI's in unlocked state.**
**Status:** not-reproducible
**Milestone:** never
**Created:** Fri May 31, 2013 06:32 AM UTC by Nagendra Kumar
**Last Updated:** Tue Dec 30, 2014 09:05 AM UTC
**Owner:** Praveen
Migrated from http://devel.opensaf.org/ticket/2830
changeset : 3784 ( 4.2.2rc1 )
Model : NORED
configuration : 1App,1SG,3SUs with 1 comp each, 3SIs with 1CSI each.
PBE enabled.
Initial states of si's
safSi=NoRedXApp_SI1,safApp=NoRedXApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=FULLY_ASSIGNED(2)
safSi=NoRedXApp_SI2,safApp=NoRedXApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(1)
safSi=NoRedXApp_SI3,safApp=NoRedXApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=FULLY_ASSIGNED(2)
SU states:
safSu=NoRedXApp_SU_1,safSg=NoRedXApp_SG,safApp=NoRedXApp
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=NoRedXApp_SU_2,safSg=NoRedXApp_SG,safApp=NoRedXApp
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=NoRedXApp_SU_3,safSg=NoRedXApp_SG,safApp=NoRedXApp
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
SUSI Assignments :
safSISU=safSu=NoRedXApp_SU_3\,safSg=NoRedXApp_SG\,safApp=NoRedXApp,safSi=NoRedXApp_SI3,safApp=NoRedXApp
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=NoRedXApp_SU_1\,safSg=NoRedXApp_SG\,safApp=NoRedXApp,safSi=NoRedXApp_SI1,safApp=NoRedXApp
saAmfSISUHAState=ACTIVE(1)
Not sure how SI2 went unassigned. Taking the above state, here tried to create
si-si dependency among SI1 and SI2, where SI1 is fullyassigned/unlocked and SI2
is unassigned/unlocked, the dependency creation succeeds which should not
happen.
console traces:
linux-xc76:~ #immcfg -c SaAmfSIDependency
"safDepend=safSi=NoRedXApp_SI1\,safApp=NoRedXApp,safSi=NoRedXApp_SI2,safApp=NoRedXApp"
-a saAmfToleranceTime=60000000000
linux-xc76:~ #immfind | grep safDep
safDepend=safSi=NoRedXApp_SI1\,safApp=NoRedXApp,safSi=NoRedXApp_SI2,safApp=NoRedXApp
immlist:
immlist
"safDepend=safSi=NoRedXApp_SI1\,safApp=NoRedXApp,safSi=NoRedXApp_SI2,safApp=NoRedXApp"
Name Type Value(s)
========================================================================
safDepend SA_NAME_T safDepend=safSi=NoRedXApp_SI1\,safApp=NoRedXApp (47)
saAmfToleranceTime SA_TIME_T 60000000000 (0xdf8475800, Thu Jan 1 05:31:00 1970)
SaImmAttrImplementerName? SA_STRING_T safAmfService
SaImmAttrClassName? SA_STRING_T SaAmfSIDependency
SaImmAttrAdminOwnerName? SA_STRING_T <Empty>
Changed 8 months ago by surenderk
■attachment active_ctrl1.tgz added
active ctrl logs minimal
Changed 8 months ago by surenderk
■attachment payload_log1.tgz added
logs on payload minimal
Changed 8 months ago by hafe ¶
■milestone changed from 4.2.2 to future_releases
Changed 8 months ago by praveenmalviya ¶
For creating SI dependency "dependent SI should be unassigned". Locking SI is
one way to achieve this. Here SI dependency was successfully created as
dependent SI was unassigned. Please modify the ticket accordingly.
Changed 8 months ago by nagendra ¶
I guess you should configuration check why susi doesn't exists for SU2 and
SI2.
As Praveen explained if si doesn't have any assignment then it will alllow to
create si dep with that si.
Can you please get back to why susi didn't exists and if there is any problem
there?
---
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.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
