- **Comment**:
The version setting does not make sense for this defect ticket.
Version must be set to the oldest version where it is known that the
defect exists.
This defect was fixed on 4.6 branch and default, which suggests that
the defect was introduced on the 4.6 branch.
Is this correct ?
If the defect was introduced earlier, or has always been present, then
it should be fixed also on the 4.5 branch.
---
** [tickets:#1389] AMF: Node state is not correct after unlock-in nodegroup**
**Status:** fixed
**Milestone:** 4.6.1
**Created:** Tue Jun 16, 2015 09:24 AM UTC by Quyen Dao
**Last Updated:** Tue Jul 14, 2015 01:52 PM UTC
**Owner:** Praveen
Steps to reproduce
------------------
* Start UML cluster
* Create a node group containing PL-3 and PL-4 with admin state as
LOCKED-INSTANTIATION
* Admin lock then lock-in PL-4 -> admin state of PL4 is LOCKED-INSTANTIATION,
PL3 is UNLOCKED
* Admin unlock-in node group
Observed behaviour
------------------
- Admin states of PL-3 and PL-4 are LOCKED
Expected behaviour
------------------
- Admin state of PL-4 is LOCKED and PL-3 remains UNLOCKED.
---
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.
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
