- **Milestone**: 4.5.2 --> 4.6.2
---
** [tickets:#473] AMF: SU rank ordering not followed at adm op SG unlock inst**
**Status:** unassigned
**Milestone:** 4.6.2
**Created:** Mon Jun 24, 2013 12:32 PM UTC by Hans Feldt
**Last Updated:** Thu Aug 06, 2015 09:53 AM UTC
**Owner:** nobody
>From
- **Type**: enhancement -- defect
- **Milestone**: future -- 4.5.2
- **Comment**:
As part of ticket cleanup, evaluated and found that this issue needs to be
fixed as defect.
---
** [tickets:#473] AMF: SU rank ordering not followed at adm op SG unlock inst**
**Status:** unassigned
- **Type**: defect -- enhancement
---
** [tickets:#473] AMF: SU rank ordering not followed at adm op SG unlock inst**
**Status:** unassigned
**Milestone:** future
**Created:** Mon Jun 24, 2013 12:32 PM UTC by Hans Feldt
**Last Updated:** Fri Aug 30, 2013 01:09 PM UTC
**Owner:** nobody
From
sg_app_sg_admin_unlock_inst() function selects SUs to be instantiated in order.
So, i am not able to understand the problem mentioned. Specs doesn't dictate to
be instantiated in order rather it says it should be selected to be
instantiated in order.
---
** [tickets:#473] AMF: SU rank
- **Version**: -- 4.3
---
** [tickets:#473] AMF: SU rank ordering not followed at adm op SG unlock inst**
**Status:** unassigned
**Created:** Mon Jun 24, 2013 12:32 PM UTC by Hans Feldt
**Last Updated:** Mon Jun 24, 2013 12:32 PM UTC
**Owner:** nobody
From spec 3.6.1.1:
Ordered list of
