Yes. If proxy and proxied are in the same SU, then proxy need to be cleaned in
the last as cleanup command of proxied is first given to proxy. If proxy are
killed first then there will not be any way to kill proxied components.
I assume you have acked the patch and I am going to push it.
---
** [tickets:#2169] amf: su containing proxy comps is not working properly after
a su restart recovery**
**Status:** review
**Milestone:** 5.0.2
**Created:** Fri Nov 04, 2016 09:45 AM UTC by Long HB Nguyen
**Last Updated:** Tue Nov 08, 2016 11:31 AM UTC
**Owner:** Nagendra Kumar
**Attachments:**
-
[osaftestLog-2016-11-04_14-55-08.tgz](https://sourceforge.net/p/opensaf/tickets/2169/attachment/osaftestLog-2016-11-04_14-55-08.tgz)
(1.2 MB; application/x-gzip-compressed)
- Description:
When a proxy component restart is escalated to a su restart, then the SU is not
working properly after that (e.g. lock failed).
- Reproduction:
1) Use the proxy demo in amf samples.
2) Unlock-in/unlock proxy SU, proxied SU.
3) Kill the proxy process some times to take the recovery escalation from comp
restart to su restart.
4) Lock the proxy SU => timeout.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
