[tickets] [opensaf:tickets] #2465 imm: change log level for "ER Problem in sending to IMMD over MDS"
- **status**: accepted --> review - **Comment**: https://sourceforge.net/p/opensaf/mailman/message/35848336/ --- ** [tickets:#2465] imm: change log level for "ER Problem in sending to IMMD over MDS"** **Status:** review **Milestone:** 5.17.06 **Created:** Fri May 19, 2017 12:22 PM UTC by Zoran Milinkovic **Last Updated:** Fri May 19, 2017 12:22 PM UTC **Owner:** Zoran Milinkovic Change log level from error ro warning for message "Problem in sending to IMMD over MDS". In all cases when this message is logged, IMMND returns ERR_TRY_AGAIN, and log level warning is more correct than error. --- 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2465 imm: change log level for "ER Problem in sending to IMMD over MDS"
--- ** [tickets:#2465] imm: change log level for "ER Problem in sending to IMMD over MDS"** **Status:** accepted **Milestone:** 5.17.06 **Created:** Fri May 19, 2017 12:22 PM UTC by Zoran Milinkovic **Last Updated:** Fri May 19, 2017 12:22 PM UTC **Owner:** Zoran Milinkovic Change log level from error ro warning for message "Problem in sending to IMMD over MDS". In all cases when this message is logged, IMMND returns ERR_TRY_AGAIN, and log level warning is more correct than error. --- 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2464 smf: try to wait for opensafd status before executing reboot
- **status**: unassigned --> review --- ** [tickets:#2464] smf: try to wait for opensafd status before executing reboot ** **Status:** review **Milestone:** 5.17.08 **Created:** Fri May 19, 2017 10:55 AM UTC by Rafael Odzakow **Last Updated:** Fri May 19, 2017 10:55 AM UTC **Owner:** Rafael Odzakow There are cases when opensafd startup is still ongoing and SMF will send out a reboot command for a node. Because opensafd has taken a lock the reboot command will not be able to call opensafd stop. It is suggested that SMF tries to wait for the release of the lock with "opensafd status". The waiting time is short and SMF continues with reboot even if the lock is not released. ticket #2459 allows SMF to query the status of opensafd. --- 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2105 AMF : SG is unstable, if app responds during node link loss detection time period
- **status**: review --> fixed - **assigned_to**: Minh Hon Chau --> nobody - **Comment**: commit b24a27c0a4c9ed6ee4f8a9dbce499466cc5e2ae1 Author: Minh Chau Date: Fri May 19 15:51:28 2017 +1000 commit 3327fbe68a0dfb978ba6ee316927d96381f42037 Author: Minh Chau Date: Fri May 19 15:51:28 2017 +1000 changeset: 8802:6737117c6904 tag: tip user:Minh Hon Chau date:Fri May 19 20:44:32 2017 +1000 --- ** [tickets:#2105] AMF : SG is unstable, if app responds during node link loss detection time period** **Status:** fixed **Milestone:** 5.17.06 **Created:** Sun Oct 09, 2016 07:12 AM UTC by Srikanth R **Last Updated:** Thu May 18, 2017 07:10 AM UTC **Owner:** nobody Setup : Changeset : 8190 5 node SLES setup with 2 controllers and 3 payloads ( TIPC -- headless enabled) 2n application deployed on 2 payloads. Issue : -> Perform admin operation on an AMF enity. -> Do not respond to the callback and invoke headless scenario. -> On a VM with TIPC setup, 3 seconds is taken to detect the node down. -> If the application responds to a callback in admin operation during this time period when the last controller is down, the message shall not reach any controller. Amfnd on payload shall send the "Assigned" message but not store this message. For this scenario, SG shall move to unstable state. Below is the snippet from syslog, where application responded at 15:48:28 and at 15:48:31 payloads detected that last controller is down. Oct 7 15:48:28 SYSTEST-PLD-1 osafamfnd[9976]: NO Assigned 'safSi=TestApp_SI1,safApp=TestApp_TwoN' ACTIVE to 'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN' Oct 7 15:48:31 SYSTEST-PLD-1 osafamfnd[9976]: WA AMF director unexpectedly crashed Oct 7 15:48:31 SYSTEST-PLD-1 osafamfnd[9976]: NO Checking 'safSu=PL-3,safSg=NoRed,safApp=OpenSAF' for pending messages Oct 7 15:48:31 SYSTEST-PLD-1 osafamfnd[9976]: NO Checking 'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN' for pending messages Oct 7 15:48:31 SYSTEST-PLD-1 osafimmnd[9957]: WA SC Absence IS allowed:900 IMMD service is DOWN Oct 7 15:48:31 SYSTEST-PLD-1 osafimmnd[9957]: NO IMMD SERVICE IS DOWN, HYDRA IS CONFIGURED => UNREGISTERING IMMND form MDS -> Below is the scenario, when payload detected that there is no controller at 18:31:34 and amfnd shall call avnd_di_susi_resp_send after the controllers join back the cluster. Application responded at 18:31:41. Oct 7 18:31:34 SYSTEST-PLD-1 osafimmnd[12448]: WA SC Absence IS allowed:900 IMMD service is DOWN Oct 7 18:31:34 SYSTEST-PLD-1 osafimmnd[12448]: NO IMMD SERVICE IS DOWN, HYDRA IS CONFIGURED => UNREGISTERING IMMND form MDS Oct 7 18:31:41 SYSTEST-PLD-1 osafamfnd[12467]: NO Assigned 'safSi=TestApp_SI4,safApp=TestApp_TwoN' ACTIVE to 'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN' Oct 7 18:31:41 SYSTEST-PLD-1 osafamfnd[12467]: NO avnd_di_susi_resp_send() deferred as AMF director is offline --- 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2447 imm: Avoid IMMND from sending introduce message when IMMD is not back from headless
- **status**: review --> fixed - **Comment**: 5.17.08 (develop) [code:a2798c] ~~~ commit a2798cef6b42f6c000d5bc0d4b9593eca367ea87 Author: Hung Nguyen Date: Mon May 8 13:30:10 2017 +0700 imm: Skip sending re-intro message if IMMD is not up [#2447] Skip sending re-intro message if IMMD is not up. ~~~ --- ** [tickets:#2447] imm: Avoid IMMND from sending introduce message when IMMD is not back from headless** **Status:** fixed **Milestone:** 5.17.08 **Created:** Wed May 03, 2017 04:04 AM UTC by Hung Nguyen **Last Updated:** Tue May 09, 2017 08:29 AM UTC **Owner:** Hung Nguyen During headless, IMMND keeps sending introduce message even when IMMD is not up yet. ~~~ May 3 10:53:15 PL-3 osafimmnd[195]: NO MDS unregisterede. sleeping ... May 3 10:53:16 PL-3 osafimmnd[195]: NO Sleep done registering IMMND with MDS May 3 10:53:16 PL-3 osafimmnd[195]: NO SUCCESS IN REGISTERING IMMND WITH MDS May 3 10:53:16 PL-3 osafimmnd[195]: NO Re-introduce-me highestProcessed:651 highestReceived:651 May 3 10:53:18 PL-3 osafclmna[185]: NO Starting to promote this node to a system controller May 3 10:53:22 PL-3 osafimmnd[195]: WA MDS Send Failed to service:IMMD rc:2 May 3 10:53:23 PL-3 osafimmnd[195]: NO Re-introduce-me highestProcessed:651 highestReceived:651 May 3 10:53:23 PL-3 osafimmnd[195]: WA MDS Send Failed to service:IMMD rc:2 May 3 10:53:24 PL-3 osafimmnd[195]: NO Re-introduce-me highestProcessed:651 highestReceived:651 May 3 10:53:24 PL-3 osafimmnd[195]: WA MDS Send Failed to service:IMMD rc:2 May 3 10:53:25 PL-3 osafimmnd[195]: NO Re-introduce-me highestProcessed:651 highestReceived:651 May 3 10:53:25 PL-3 osafimmnd[195]: WA MDS Send Failed to service:IMMD rc:2 ... ~~~ --- 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2446 imm: CcbErrorStrings about OI/PBE are not set in all nodes
- **status**: review --> fixed
- **Comment**:
5.17.06 (release) [code:a16e75]
~~~
commit a16e75230da4d41e7359728e2451c7683da69183
Author: Hung Nguyen
Date: Mon May 8 11:09:34 2017 +0700
imm: Remove CcbErrStrings that are set only on nodes with OI/PBE [#2446]
Remove CcbErrStrings that are set only on nodes with OI/PBE.
~~~
5.17.08 (develop) [code:f9906a]
~~~
commit f9906af0227fb859bfda991a5ed03d664c6e152e
Author: Hung Nguyen
Date: Mon May 8 11:09:34 2017 +0700
imm: Remove CcbErrStrings that are set only on nodes with OI/PBE [#2446]
Remove CcbErrStrings that are set only on nodes with OI/PBE.
~~~
---
** [tickets:#2446] imm: CcbErrorStrings about OI/PBE are not set in all nodes**
**Status:** fixed
**Milestone:** 5.17.06
**Created:** Wed May 03, 2017 03:32 AM UTC by Hung Nguyen
**Last Updated:** Tue May 09, 2017 08:29 AM UTC
**Owner:** Hung Nguyen
Example:
~~~
if (implConn) {
/*The implementer is local, make the up-call */
...
/*Fetch client node for OI ! */
immnd_client_node_get(cb, implHandle, &oi_cl_node);
if (oi_cl_node == NULL || oi_cl_node->mIsStale) {
...
immModel_setCcbErrorString(
cb, evt->info.objCreate.ccbId,
IMM_RESOURCE_ABORT "Client died");
}
~~~
The error string is only sent to OM client when the OM client is on the same
node with the OI.
That causes inconsistency between OM being on the same node with OI and OM
being on different node than OI.
---
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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2463 ntf: ntftest should not run suite 35 if longDnsAllowed is not enabled
Hi Minh,
Speaking of ntf/apitest/README, it also mentions that suite 32 and 34 require
some test classed be loaded in advance. And currently, ntftest does check for
the existence of the file 'ntfsv_test_classes.xml' before running those suites;
otherwise the following message is printed out and those suites will not be run.
~~~
if (rc != 0) {
printf(
"ntfsv_test_classes.xml file not installed (see README)");
return;
}
~~~
That means ntftest already had some pre-conditions checks before running test.
That's why I think we can have similar check for long-dn support for suite 35.
And with the class file check was already there, the missing of long-dn check
shall be considered be a defect, in my opinion.
Besides, other services' apitests also check (CLM) or make sure (LOG) long-dn
support is enabled before running or skipping specific test cases.
It's my point of view on this issue. As the NTF maintainer, you can have final
decision whether this is a defect or enhancement.
Thanks,
/Nguyen
---
** [tickets:#2463] ntf: ntftest should not run suite 35 if longDnsAllowed is
not enabled**
**Status:** review
**Milestone:** 5.17.06
**Created:** Fri May 19, 2017 02:33 AM UTC by Nguyen TK Luu
**Last Updated:** Fri May 19, 2017 10:27 AM UTC
**Owner:** Nguyen TK Luu
Suite 35 of the NTF API test requires that long-dns support is enabled in the
system.
Currently, when the user just runs ntftest without specifying any test suite,
and without enabling long-dns support, suite 35 is also run and fails as a
result (see below log). This is not expected.
The test should instead check for long-dns support to whether run or not run
suite 35.
root@SC-1:~# immcfg -f /tmp/ntfsv_test_classes.xml
root@SC-1:~# ntftest
/usr/local/bin/rdegetrole
This is a controller node
Suite 1: Life cycle, initialize, API 1
1 PASSED saNtfInitialize SA_AIS_OK;
2 PASSED saNtfInitialize with NULL pointer to handle;
3 PASSED saNtfInitialize with NULL pointer to callbacks;
4 PASSED saNtfInitialize with NULL callbacks AND version;
5 PASSED saNtfInitialize with uninitialized handle;
6 PASSED saNtfInitialize with uninitialized version;
7 PASSED saNtfInitialize with too high release level;
8 PASSED saNtfInitialize with minor version set too high;
9 PASSED saNtfInitialize with major version set too high;
10 PASSED saNtfInitialize with minor version set to lower;
11 PASSED saNtfInitialize with major version set to lower;
12 PASSED saNtfInitialize with version A.0.0;
Suite 2: Life cycle, finalize, API 2
1 PASSED saNtfFinalize SA_AIS_OK;
2 PASSED saNtfFinalize SA_AIS_ERR_BAD_HANDLE - invalid handle;
3 PASSED saNtfFinalize SA_AIS_ERR_BAD_HANDLE - handle already returned;
Return value from thread:1
4 PASSED Finalize and Unsubscribe in parallel SA_AIS_OK;
Return value from thread:1
5 PASSED Finalize and saNtfStateChangeNotificationAllocate in parallel
SA_AIS_OK;
Suite 3: Life cycle, selectObject, API 3
1 PASSED saNtfSelectionObjectGet SA_AIS_OK;
2 PASSED saNtfSelectionObjectGet NULL handle SA_AIS_ERR_BAD_HANDLE;
3 PASSED saNtfSelectionObjectGet invalid handle SA_AIS_ERR_BAD_HANDLE;
4 PASSED saNtfSelectionObjectGet NULL selectionObject SA_AIS_ERR_INVALID_PARAM;
Suite 4: Life cycle, dispatch, API 4
1 PASSED saNtfDispatch - SA_AIS_OK SA_DISPATCH_ALL;
2 PASSED saNtfDispatch - invalid handle SA_AIS_ERR_BAD_HANDLE;
3 PASSED saNtfDispatch - zero flag SA_AIS_ERR_INVALID_PARAM;
Suite 6: Producer API 2 allocate
1 PASSED saNtfMiscellaneousNotificationAllocate, Not supported;
2 PASSED saNtfMiscellaneousNotificationAllocate SA_AIS_ERR_BAD_HANDLE;
3 PASSED saNtfMiscellaneousNotificationAllocate SA_AIS_ERR_INVALID_PARAM;
4 PASSED saNtfAlarmNotificationAllocate SA_AIS_OK;
5 PASSED saNtfAlarmNotificationAllocate SA_AIS_ERR_BAD_HANDLE;
6 PASSED saNtfAlarmNotificationAllocate SA_AIS_ERR_INVALID_PARAM;
7 PASSED saNtfAttributeChangeNotificationAllocate SA_AIS_OK;
8 PASSED saNtfAttributeChangeNotificationAllocate SA_AIS_ERR_BAD_HANDLE;
9 PASSED saNtfAttributeChangeNotificationAllocate SA_AIS_ERR_INVALID_PARAM;
10 PASSED saNtfStateChangeNotificationAllocate SA_AIS_OK;
11 PASSED saNtfStateChangeNotificationAllocate SA_AIS_ERR_BAD_HANDLE;
12 PASSED saNtfStateChangeNotificationAllocate NULL notification
SA_AIS_ERR_INVALID_PARAM;
13 PASSED saNtfSecurityAlarmNotificationAllocate SA_AIS_OK;
14 PASSED saNtfSecurityAlarmNotificationAllocate SA_AIS_ERR_BAD_HANDLE;
15 PASSED saNtfSecurityAlarmNotificationAllocate SA_AIS_ERR_INVALID_PARAM;
16 PASSED saNtfObjectCreateDeleteNotificationAllocate SA_AIS_OK;
17 PASSED saNtfObjectCreateDeleteNotificationAllocate SA_AIS_ERR_BAD_HANDLE;
18 PASSED saNtfObjectCreateDeleteNotificationAllocate SA_AIS_ERR_INVALID_PARAM;
Suite 7: Consumer operations - filter allocate
1 PASSED saNtfStateChangeNotificationFilterAllocate - SA_AIS_OK;
2 PASSED saNtfStateChangeNotificationFilterAllocate - handle null
SA_AIS_ERR_BAD_HANDLE;
3 PASSED saNtfStateChangeNotificationFilterAllocate - ha
[tickets] [opensaf:tickets] #2464 smf: try to wait for opensafd status before executing reboot
--- ** [tickets:#2464] smf: try to wait for opensafd status before executing reboot ** **Status:** unassigned **Milestone:** 5.17.08 **Created:** Fri May 19, 2017 10:55 AM UTC by Rafael Odzakow **Last Updated:** Fri May 19, 2017 10:55 AM UTC **Owner:** Rafael Odzakow There are cases when opensafd startup is still ongoing and SMF will send out a reboot command for a node. Because opensafd has taken a lock the reboot command will not be able to call opensafd stop. It is suggested that SMF tries to wait for the release of the lock with "opensafd status". The waiting time is short and SMF continues with reboot even if the lock is not released. ticket #2459 allows SMF to query the status of opensafd. --- 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2463 ntf: ntftest should not run suite 35 if longDnsAllowed is not enabled
why is #2463 a defect? The src/ntf/apitest/README has documented that suite 35 needs to have IMM LongDN enabled. When you run ntftest (no arg), or ntftest 35, you see it failed. What's the next step? You would look into to suite 35 to see why it fails, or you just want ntftest passes unconditionally? Both running ntftest (or ntftest 35) fail as it should, because user has not enabled IMM LongDN support. It is a defect if ntftest is doing something wrong as it should not. If you don't want to see any suite failed because of user's misconfiguration, you can skip it, then it is an enhancement. And when you run a test with misconfiguration, then the test should fail. --- ** [tickets:#2463] ntf: ntftest should not run suite 35 if longDnsAllowed is not enabled** **Status:** review **Milestone:** 5.17.06 **Created:** Fri May 19, 2017 02:33 AM UTC by Nguyen TK Luu **Last Updated:** Fri May 19, 2017 08:42 AM UTC **Owner:** Nguyen TK Luu Suite 35 of the NTF API test requires that long-dns support is enabled in the system. Currently, when the user just runs ntftest without specifying any test suite, and without enabling long-dns support, suite 35 is also run and fails as a result (see below log). This is not expected. The test should instead check for long-dns support to whether run or not run suite 35. root@SC-1:~# immcfg -f /tmp/ntfsv_test_classes.xml root@SC-1:~# ntftest /usr/local/bin/rdegetrole This is a controller node Suite 1: Life cycle, initialize, API 1 1 PASSED saNtfInitialize SA_AIS_OK; 2 PASSED saNtfInitialize with NULL pointer to handle; 3 PASSED saNtfInitialize with NULL pointer to callbacks; 4 PASSED saNtfInitialize with NULL callbacks AND version; 5 PASSED saNtfInitialize with uninitialized handle; 6 PASSED saNtfInitialize with uninitialized version; 7 PASSED saNtfInitialize with too high release level; 8 PASSED saNtfInitialize with minor version set too high; 9 PASSED saNtfInitialize with major version set too high; 10 PASSED saNtfInitialize with minor version set to lower; 11 PASSED saNtfInitialize with major version set to lower; 12 PASSED saNtfInitialize with version A.0.0; Suite 2: Life cycle, finalize, API 2 1 PASSED saNtfFinalize SA_AIS_OK; 2 PASSED saNtfFinalize SA_AIS_ERR_BAD_HANDLE - invalid handle; 3 PASSED saNtfFinalize SA_AIS_ERR_BAD_HANDLE - handle already returned; Return value from thread:1 4 PASSED Finalize and Unsubscribe in parallel SA_AIS_OK; Return value from thread:1 5 PASSED Finalize and saNtfStateChangeNotificationAllocate in parallel SA_AIS_OK; Suite 3: Life cycle, selectObject, API 3 1 PASSED saNtfSelectionObjectGet SA_AIS_OK; 2 PASSED saNtfSelectionObjectGet NULL handle SA_AIS_ERR_BAD_HANDLE; 3 PASSED saNtfSelectionObjectGet invalid handle SA_AIS_ERR_BAD_HANDLE; 4 PASSED saNtfSelectionObjectGet NULL selectionObject SA_AIS_ERR_INVALID_PARAM; Suite 4: Life cycle, dispatch, API 4 1 PASSED saNtfDispatch - SA_AIS_OK SA_DISPATCH_ALL; 2 PASSED saNtfDispatch - invalid handle SA_AIS_ERR_BAD_HANDLE; 3 PASSED saNtfDispatch - zero flag SA_AIS_ERR_INVALID_PARAM; Suite 6: Producer API 2 allocate 1 PASSED saNtfMiscellaneousNotificationAllocate, Not supported; 2 PASSED saNtfMiscellaneousNotificationAllocate SA_AIS_ERR_BAD_HANDLE; 3 PASSED saNtfMiscellaneousNotificationAllocate SA_AIS_ERR_INVALID_PARAM; 4 PASSED saNtfAlarmNotificationAllocate SA_AIS_OK; 5 PASSED saNtfAlarmNotificationAllocate SA_AIS_ERR_BAD_HANDLE; 6 PASSED saNtfAlarmNotificationAllocate SA_AIS_ERR_INVALID_PARAM; 7 PASSED saNtfAttributeChangeNotificationAllocate SA_AIS_OK; 8 PASSED saNtfAttributeChangeNotificationAllocate SA_AIS_ERR_BAD_HANDLE; 9 PASSED saNtfAttributeChangeNotificationAllocate SA_AIS_ERR_INVALID_PARAM; 10 PASSED saNtfStateChangeNotificationAllocate SA_AIS_OK; 11 PASSED saNtfStateChangeNotificationAllocate SA_AIS_ERR_BAD_HANDLE; 12 PASSED saNtfStateChangeNotificationAllocate NULL notification SA_AIS_ERR_INVALID_PARAM; 13 PASSED saNtfSecurityAlarmNotificationAllocate SA_AIS_OK; 14 PASSED saNtfSecurityAlarmNotificationAllocate SA_AIS_ERR_BAD_HANDLE; 15 PASSED saNtfSecurityAlarmNotificationAllocate SA_AIS_ERR_INVALID_PARAM; 16 PASSED saNtfObjectCreateDeleteNotificationAllocate SA_AIS_OK; 17 PASSED saNtfObjectCreateDeleteNotificationAllocate SA_AIS_ERR_BAD_HANDLE; 18 PASSED saNtfObjectCreateDeleteNotificationAllocate SA_AIS_ERR_INVALID_PARAM; Suite 7: Consumer operations - filter allocate 1 PASSED saNtfStateChangeNotificationFilterAllocate - SA_AIS_OK; 2 PASSED saNtfStateChangeNotificationFilterAllocate - handle null SA_AIS_ERR_BAD_HANDLE; 3 PASSED saNtfStateChangeNotificationFilterAllocate - handle returned SA_AIS_ERR_BAD_HANDLE; 4 PASSED saNtfStateChangeNotificationFilterAllocate - SA_AIS_ERR_INVALID_PARAM; 5 PASSED saNtfSecurityAlarmNotificationFilterAllocate - SA_AIS_OK; 6 PASSED saNtfSecurityAlarmNotificationFilterAllocate - handle null SA_AIS_ERR_BAD_HANDLE; 7 PASSED saNtfSecurityAlarmNotificationFilterAllocate - handle returned SA_AIS_ERR_BAD_HANDLE; 8 PASSED saNtfSecurity
[tickets] [opensaf:tickets] #2463 ntf: ntftest should not run suite 35 if longDnsAllowed is not enabled
- **status**: assigned --> review --- ** [tickets:#2463] ntf: ntftest should not run suite 35 if longDnsAllowed is not enabled** **Status:** review **Milestone:** 5.17.06 **Created:** Fri May 19, 2017 02:33 AM UTC by Nguyen TK Luu **Last Updated:** Fri May 19, 2017 02:33 AM UTC **Owner:** Nguyen TK Luu Suite 35 of the NTF API test requires that long-dns support is enabled in the system. Currently, when the user just runs ntftest without specifying any test suite, and without enabling long-dns support, suite 35 is also run and fails as a result (see below log). This is not expected. The test should instead check for long-dns support to whether run or not run suite 35. root@SC-1:~# immcfg -f /tmp/ntfsv_test_classes.xml root@SC-1:~# ntftest /usr/local/bin/rdegetrole This is a controller node Suite 1: Life cycle, initialize, API 1 1 PASSED saNtfInitialize SA_AIS_OK; 2 PASSED saNtfInitialize with NULL pointer to handle; 3 PASSED saNtfInitialize with NULL pointer to callbacks; 4 PASSED saNtfInitialize with NULL callbacks AND version; 5 PASSED saNtfInitialize with uninitialized handle; 6 PASSED saNtfInitialize with uninitialized version; 7 PASSED saNtfInitialize with too high release level; 8 PASSED saNtfInitialize with minor version set too high; 9 PASSED saNtfInitialize with major version set too high; 10 PASSED saNtfInitialize with minor version set to lower; 11 PASSED saNtfInitialize with major version set to lower; 12 PASSED saNtfInitialize with version A.0.0; Suite 2: Life cycle, finalize, API 2 1 PASSED saNtfFinalize SA_AIS_OK; 2 PASSED saNtfFinalize SA_AIS_ERR_BAD_HANDLE - invalid handle; 3 PASSED saNtfFinalize SA_AIS_ERR_BAD_HANDLE - handle already returned; Return value from thread:1 4 PASSED Finalize and Unsubscribe in parallel SA_AIS_OK; Return value from thread:1 5 PASSED Finalize and saNtfStateChangeNotificationAllocate in parallel SA_AIS_OK; Suite 3: Life cycle, selectObject, API 3 1 PASSED saNtfSelectionObjectGet SA_AIS_OK; 2 PASSED saNtfSelectionObjectGet NULL handle SA_AIS_ERR_BAD_HANDLE; 3 PASSED saNtfSelectionObjectGet invalid handle SA_AIS_ERR_BAD_HANDLE; 4 PASSED saNtfSelectionObjectGet NULL selectionObject SA_AIS_ERR_INVALID_PARAM; Suite 4: Life cycle, dispatch, API 4 1 PASSED saNtfDispatch - SA_AIS_OK SA_DISPATCH_ALL; 2 PASSED saNtfDispatch - invalid handle SA_AIS_ERR_BAD_HANDLE; 3 PASSED saNtfDispatch - zero flag SA_AIS_ERR_INVALID_PARAM; Suite 6: Producer API 2 allocate 1 PASSED saNtfMiscellaneousNotificationAllocate, Not supported; 2 PASSED saNtfMiscellaneousNotificationAllocate SA_AIS_ERR_BAD_HANDLE; 3 PASSED saNtfMiscellaneousNotificationAllocate SA_AIS_ERR_INVALID_PARAM; 4 PASSED saNtfAlarmNotificationAllocate SA_AIS_OK; 5 PASSED saNtfAlarmNotificationAllocate SA_AIS_ERR_BAD_HANDLE; 6 PASSED saNtfAlarmNotificationAllocate SA_AIS_ERR_INVALID_PARAM; 7 PASSED saNtfAttributeChangeNotificationAllocate SA_AIS_OK; 8 PASSED saNtfAttributeChangeNotificationAllocate SA_AIS_ERR_BAD_HANDLE; 9 PASSED saNtfAttributeChangeNotificationAllocate SA_AIS_ERR_INVALID_PARAM; 10 PASSED saNtfStateChangeNotificationAllocate SA_AIS_OK; 11 PASSED saNtfStateChangeNotificationAllocate SA_AIS_ERR_BAD_HANDLE; 12 PASSED saNtfStateChangeNotificationAllocate NULL notification SA_AIS_ERR_INVALID_PARAM; 13 PASSED saNtfSecurityAlarmNotificationAllocate SA_AIS_OK; 14 PASSED saNtfSecurityAlarmNotificationAllocate SA_AIS_ERR_BAD_HANDLE; 15 PASSED saNtfSecurityAlarmNotificationAllocate SA_AIS_ERR_INVALID_PARAM; 16 PASSED saNtfObjectCreateDeleteNotificationAllocate SA_AIS_OK; 17 PASSED saNtfObjectCreateDeleteNotificationAllocate SA_AIS_ERR_BAD_HANDLE; 18 PASSED saNtfObjectCreateDeleteNotificationAllocate SA_AIS_ERR_INVALID_PARAM; Suite 7: Consumer operations - filter allocate 1 PASSED saNtfStateChangeNotificationFilterAllocate - SA_AIS_OK; 2 PASSED saNtfStateChangeNotificationFilterAllocate - handle null SA_AIS_ERR_BAD_HANDLE; 3 PASSED saNtfStateChangeNotificationFilterAllocate - handle returned SA_AIS_ERR_BAD_HANDLE; 4 PASSED saNtfStateChangeNotificationFilterAllocate - SA_AIS_ERR_INVALID_PARAM; 5 PASSED saNtfSecurityAlarmNotificationFilterAllocate - SA_AIS_OK; 6 PASSED saNtfSecurityAlarmNotificationFilterAllocate - handle null SA_AIS_ERR_BAD_HANDLE; 7 PASSED saNtfSecurityAlarmNotificationFilterAllocate - handle returned SA_AIS_ERR_BAD_HANDLE; 8 PASSED saNtfSecurityAlarmNotificationFilterAllocate - SA_AIS_ERR_INVALID_PARAM; 9 PASSED saNtfObjectCreateDeleteNotificationFilterAllocate - SA_AIS_OK; 10 PASSED saNtfObjectCreateDeleteNotificationFilterAllocate - handle null SA_AIS_ERR_BAD_HANDLE; 11 PASSED saNtfObjectCreateDeleteNotificationFilterAllocate - handle returned SA_AIS_ERR_BAD_HANDLE; 12 PASSED saNtfObjectCreateDeleteNotificationFilterAllocate - SA_AIS_ERR_INVALID_PARAM; 13 PASSED saNtfAttributeChangeNotificationFilterAllocate - SA_AIS_OK; 14 PASSED saNtfAttributeChangeNotificationFilterAllocate - handle NULL SA_AIS_ERR_BAD_HANDLE; 15 PASSED saNtfAttributeChangeNotificationFilterAllocate
