[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery
Raised https://sourceforge.net/p/opensaf/tickets/2186/ --- ** [tickets:#2169] amf: su containing proxy comps is not working properly after a su restart recovery** **Status:** fixed **Milestone:** 5.0.2 **Created:** Fri Nov 04, 2016 09:45 AM UTC by Long HB Nguyen **Last Updated:** Mon Nov 14, 2016 07:41 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 opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery
Hi Nagu, In case you want to fix for that case. You can open a ticket yourself. Best regards, Long Nguyen. --- ** [tickets:#2169] amf: su containing proxy comps is not working properly after a su restart recovery** **Status:** fixed **Milestone:** 5.0.2 **Created:** Fri Nov 04, 2016 09:45 AM UTC by Long HB Nguyen **Last Updated:** Mon Nov 14, 2016 07:38 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 opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery
Ok, thanks for the information, I will test it. --- ** [tickets:#2169] amf: su containing proxy comps is not working properly after a su restart recovery** **Status:** fixed **Milestone:** 5.0.2 **Created:** Fri Nov 04, 2016 09:45 AM UTC by Long HB Nguyen **Last Updated:** Mon Nov 14, 2016 07:37 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 opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery
Hi Nagu, Originally, I only tested the case that a proxy component and a proxied component are not in the same SU (i.e. samples/amf/proxy). However, when looking into the code, I think that it may have the same problem with the case that a proxy and a proxied component are in the same SU. That is the reason I asked. However, I have not tested that case with your code. Thanks, Long Nguyen. --- ** [tickets:#2169] amf: su containing proxy comps is not working properly after a su restart recovery** **Status:** fixed **Milestone:** 5.0.2 **Created:** Fri Nov 04, 2016 09:45 AM UTC by Long HB Nguyen **Last Updated:** Mon Nov 14, 2016 07:08 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 opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery
Hi Long HB Nguyen, I assumed that you had code doubt about "still return immediately" and it is not creating any problem. Can you please confirm that this problem exist with the SU having proxy and proxied components has the same issue. If yes, create a separate ticket as this ticket was raised as per samples/amf/proxy and in that sample, SUs of proxy and proxied components are different. Thanks -Nagu --- ** [tickets:#2169] amf: su containing proxy comps is not working properly after a su restart recovery** **Status:** fixed **Milestone:** 5.0.2 **Created:** Fri Nov 04, 2016 09:45 AM UTC by Long HB Nguyen **Last Updated:** Wed Nov 09, 2016 06:52 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 opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery
- **status**: review --> fixed - **Comment**: searching for changes changeset: 8294:88be3d560de2 branch: opensaf-5.0.x parent: 8291:578552651e82 user:Nagendra Kumardate:Wed Nov 09 11:38:02 2016 +0530 summary: amfnd: clean proxy if proxy and proxied are not in the same SU [#2169] changeset: 8295:4879318abbe5 branch: opensaf-5.1.x parent: 8292:a029795d9845 user:Nagendra Kumar date:Wed Nov 09 11:38:21 2016 +0530 summary: amfnd: clean proxy if proxy and proxied are not in the same SU [#2169] changeset: 8296:0bcf2b782bcc tag: tip parent: 8293:135eb53abf6f user:Nagendra Kumar date:Wed Nov 09 11:38:40 2016 +0530 summary: amfnd: clean proxy if proxy and proxied are not in the same SU [#2169] --- ** [tickets:#2169] amf: su containing proxy comps is not working properly after a su restart recovery** **Status:** fixed **Milestone:** 5.0.2 **Created:** Fri Nov 04, 2016 09:45 AM UTC by Long HB Nguyen **Last Updated:** Wed Nov 09, 2016 06:43 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 opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery
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 opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery
Hi Nagu, I have tested the patch. It is working fine and the proxy component gets CLEANUP. In your patch, you have fixed for the case that Proxy and Proxied comp are not in the same SU. In the case, they are in the same SU, the behavior is different (i.e. still return immediately). Could you share the idea behind that? Thanks, Long Nguyen. Attachments: - [2169.zip](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/47908ac2/980f/attachment/2169.zip) (1.8 kB; application/x-zip-compressed) --- ** [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 09:19 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 opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery
- **status**: assigned --> review --- ** [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 06:12 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 opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery
Hi Nagu, The changeset is 8272. I used the proxy demo and the config file (.xml) in samples/amf/proxy. --- ** [tickets:#2169] amf: su containing proxy comps is not working properly after a su restart recovery** **Status:** assigned **Milestone:** 5.0.2 **Created:** Fri Nov 04, 2016 09:45 AM UTC by Long HB Nguyen **Last Updated:** Tue Nov 08, 2016 06:05 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 opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery
Also, please share the config file(.xml) or configuration details. --- ** [tickets:#2169] amf: su containing proxy comps is not working properly after a su restart recovery** **Status:** assigned **Milestone:** 5.0.2 **Created:** Fri Nov 04, 2016 09:45 AM UTC by Long HB Nguyen **Last Updated:** Tue Nov 08, 2016 06:02 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 opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery
Hi Long HB Nguyen, Can you please update the version or change set. --- ** [tickets:#2169] amf: su containing proxy comps is not working properly after a su restart recovery** **Status:** assigned **Milestone:** 5.0.2 **Created:** Fri Nov 04, 2016 09:45 AM UTC by Long HB Nguyen **Last Updated:** Mon Nov 07, 2016 05:12 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 opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery
- **status**: unassigned --> assigned - **assigned_to**: Nagendra Kumar --- ** [tickets:#2169] amf: su containing proxy comps is not working properly after a su restart recovery** **Status:** assigned **Milestone:** 5.0.2 **Created:** Fri Nov 04, 2016 09:45 AM UTC by Long HB Nguyen **Last Updated:** Fri Nov 04, 2016 09:45 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 opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2169 amf: su containing proxy comps is not working properly after a su restart recovery
--- ** [tickets:#2169] amf: su containing proxy comps is not working properly after a su restart recovery** **Status:** unassigned **Milestone:** 5.0.2 **Created:** Fri Nov 04, 2016 09:45 AM UTC by Long HB Nguyen **Last Updated:** Fri Nov 04, 2016 09:45 AM UTC **Owner:** nobody **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 opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets