In case of SA_AIS_ERR_NOT_SUPPORTED, practically, we need to inform user about
our proprietary implementation. For example:
if ((su->sg_of_su->sg_ncs_spec == SA_TRUE)
&& (cb->node_id_avd == su->su_on_node->node_info.nodeId)) {
rc = SA_AIS_ERR_NOT_SUPPORTED;
LOG_WA("Admin operation on Active middleware SU is not
allowed");
goto done;
}
In this case, we need to inform user that it is middleware SU. If we just
reject it, user may not be aware about the rejection.
---
** [tickets:#85] AMF: admin ops should return error strings**
**Status:** accepted
**Created:** Mon May 13, 2013 04:44 AM UTC by Nagendra Kumar
**Last Updated:** Thu Sep 26, 2013 01:58 PM UTC
**Owner:** Nagendra Kumar
Migrated from http://devel.opensaf.org/ticket/2471
>From 4.2 IMM admin ops supports error strings in the admin op response. AMF
>should use that API and perhaps the syslogging of the same should be removed.
---
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.------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
