I guess, version is 'reported version' on which tests were performed and bug
was found.
---
** [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
- **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 ?
- **Version**: 4.7-Tentative -- 4.6
---
** [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
- **status**: review -- fixed
- **Comment**:
changeset: 6670:0b11c5a96a94
branch: opensaf-4.6.x
parent: 6668:3950242b02b0
user:praveen.malv...@oracle.com
date:Tue Jul 14 19:17:53 2015 +0530
summary: amfd: ignore unlocked node during unlock-in op on ng [#1389]
- **status**: accepted -- review
---
** [tickets:#1389] AMF: Node state is not correct after unlock-in nodegroup**
**Status:** review
**Milestone:** 4.6.1
**Created:** Tue Jun 16, 2015 09:24 AM UTC by Quyen Dao
**Last Updated:** Wed Jun 17, 2015 04:39 AM UTC
**Owner:** Praveen
Steps to
- **status**: unassigned -- accepted
- **assigned_to**: Praveen
- **Milestone**: future -- 4.6.1
---
** [tickets:#1389] AMF: Node state is not correct after unlock-in nodegroup**
**Status:** accepted
**Milestone:** 4.6.1
**Created:** Tue Jun 16, 2015 09:24 AM UTC by Quyen Dao
**Last
---
** [tickets:#1389] AMF: Node state is not correct after unlock-in nodegroup**
**Status:** unassigned
**Milestone:** future
**Created:** Tue Jun 16, 2015 09:24 AM UTC by Quyen Dao
**Last Updated:** Tue Jun 16, 2015 09:24 AM UTC
**Owner:** nobody
Steps to reproduce
--
*
