- **status**: unassigned --> accepted
- **assigned_to**: Praveen
---
** [tickets:#1511] AMF : UNINSTANTIATED notification missing for SU restart
operation**
**Status:** accepted
**Milestone:** 4.5.2
**Created:** Mon Oct 05, 2015 07:09 AM UTC by Srikanth R
**Last Updated:** Mon Oct 05, 2015
- **status**: accepted --> invalid
- **Milestone**: 4.5.2 --> never
---
** [tickets:#1511] AMF : UNINSTANTIATED notification missing for SU restart
operation**
**Status:** invalid
**Milestone:** never
**Created:** Mon Oct 05, 2015 07:09 AM UTC by Srikanth R
**Last Updated:** Wed Oct 07, 2015
---
** [tickets:#1511] AMF : UNINSTANTIATED notification missing for SU restart
operation**
**Status:** unassigned
**Milestone:** 4.5.2
**Created:** Mon Oct 05, 2015 07:09 AM UTC by Srikanth R
**Last Updated:** Mon Oct 05, 2015 07:09 AM UTC
**Owner:** nobody
When admin restart operation is
The SU mentioned in the ticket contains both restartable and non-restartable
components.
---
** [tickets:#1511] AMF : UNINSTANTIATED notification missing for SU restart
operation**
**Status:** unassigned
**Milestone:** 4.5.2
**Created:** Mon Oct 05, 2015 07:09 AM UTC by Srikanth R
**Last
As per spec a SU enters into UNINSTANTIATED state when all its components are
in UNINSTANTIATED state.
So when a SU contains both restartable and non-restartable comp, SU will not
enter into UNINSTANTIATED state as restartable components will remain in
RESTARTING state until they move to
