#1389 AMF: Node state is not correct after unlock-in nodegroup

[Quyen Dao]

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.

[Praveen]

changeset: 6670:0b11c5a96a94
branch: opensaf-4.6.x
parent: 6668:3950242b02b0
user: praveen.malviya@oracle.com
date: Tue Jul 14 19:17:53 2015 +0530
summary: amfd: ignore unlocked node during unlock-in op on ng [#1389]

changeset: 6671:682b61512159
parent: 6669:08f308d682ca
user: praveen.malviya@oracle.com
date: Tue Jul 14 19:18:44 2015 +0530
summary: amfd: ignore unlocked node during unlock-in op on ng [#1389]

changeset: 6672:67e6c858561e
branch: opensaf-4.6.x
parent: 6670:0b11c5a96a94
user: Gary Lee gary.lee@dektech.com.au
date: Tue Jul 14 19:19:29 2015 +0530
summary: amfd: ignore invalid operations on nodegroup [#1389]

changeset: 6673:9682ea6b4dd9
tag: tip
parent: 6671:682b61512159
user: Gary Lee gary.lee@dektech.com.au
date: Tue Jul 14 19:19:39 2015 +0530
summary: amfd: ignore invalid operations on nodegroup [#1389]

[Anders Bjornerstedt]

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.

[Nagendra Kumar]

I guess, version is 'reported version' on which tests were performed and bug was found.

[Anders Bjornerstedt]

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:nagendra-k@users.sf.net]
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