Hi all,
I've run into this issue a few times now where I attempt to lock an SU, but
opensaf rejects the request stating that it's already locked.
However, when I display the SU state, it shows it as unlocked (see commands &
output below).
It appears internally, that the opensaf state of an SU is not propagated to all
parts of opensaf.
In talking with Alex Jones, he believes this issue has been resolved but is
unsure what the actual fix is.
Can somebody confirm this issue has been fixed and provide the ticket number?
Setup:
- Opensaf 4.6.0 running on RHEL 6.6 VMs with TCP
- 2 controllers, 4 payloads
Here's the status of the SU from the amf-state command where it shows the admin
state as unlocked:
[root@payload-4 ~]# date; amf-state su | grep -A 5 NSPb9lab
Fri Mar 24 09:41:26 EDT 2017
safSu=SU1,safSg=app4,safApp=app4
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
[root@payload-4 ~]#
When I issue the lock request, it fails with the following error:
[root@payload-4 ~]# date; amf-adm lock safSu=SU1,safSg=app4,safApp=app4
Fri Mar 24 09:42:12 EDT 2017
error - saImmOmAdminOperationInvoke_2 admin-op RETURNED: SA_AIS_ERR_NO_OP (28)
error-string: Admin operation (2) has no effect on current state (2)
[root@payload-4 ~]#
Regards,
David
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-users
