Yes but version should be uppdated by maintainer to reflect where the problem
exists (earliest version).
Even if the problem is only fixed on the three latest branches it may exist on
earlier branches and this information may be
Important for some users. They may need to backport the patch themselves etc.
This particular ticket was only fixed for the two latest branches instead of
the three latest making things even mor confusing.
/AndesBj
From: Nagendra Kumar [mailto:[email protected]]
Sent: den 15 juli 2015 13:01
To: [opensaf:tickets]
Subject: [opensaf:tickets] #1389 AMF: Node state is not correct after unlock-in
nodegroup
I guess, version is 'reported version' on which tests were performed and bug
was found.
________________________________
[tickets:#1389]<http://sourceforge.net/p/opensaf/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: Wed Jul 15, 2015 10:53 AM 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 you indicated interest in
https://sourceforge.net/p/opensaf/tickets/1389/<https://sourceforge.net/p/opensaf/tickets/1389>
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/<https://sourceforge.net/auth/subscriptions>
---
** [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:** Wed Jul 15, 2015 11:01 AM 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 http://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
http://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
