SMF supports long DN in general but there are some limitations mainly becase
AMF does not support long DN before OpenSAF version 5.1. Therefore SMF has
tests that limit the usage of long DN for AMF related objects and long campaign
names.
Support for long DN is implemented in AMF and enabled in SMF from version 5.1.
Try to test with 5.1.0 or later. See also [#1968]
---
** [tickets:#2087] SMF: smfnd asserted on active controller with long dn when
executing the campaign.**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Fri Sep 30, 2016 11:47 AM UTC by Madhurika Koppula
**Last Updated:** Fri Sep 30, 2016 11:48 AM UTC
**Owner:** nobody
**Attachments:**
-
[smfnd_assert.tgz](https://sourceforge.net/p/opensaf/tickets/2087/attachment/smfnd_assert.tgz)
(936.2 kB; application/octet-stream)
**Environment Details:**
OS : Suse 64bit
Setup : 4 nodes ( 2 controllers and 2 payloads with headless feature disabled &
PBE disabled ).
**Summary**: smfnd asserted on active controller with long dn when executing
the campaign.
**Steps followed & Observed behaviour:**
1) Initially brought up four nodes and all the nodes joined the cluster (PBE is
disabled)
2) Enabled long dn as follows.
immcfg -a longDnsAllowed=1 opensafImm=opensafImm,safApp=safImmService
3) Successfully created the campaign object with long dn
immcfg -c SaSmfCampaign
safSmfCampaign=campaign_long_dn_ddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd,safApp=safSmfService
-a SmfCmpgFileUri=/hostfs/campaign85.xml
4) Executed the campaign.
Observations:
smfnd asserted on active controller. Campaign execution failed.
Below is the timestamp of Active controller (SC-1):
Oct 9 22:07:06 SCALE_SLOT-21 osafsmfd[2816]: NO CAMP: Calling configured
smfBundleCheckCmd for each bundle existing in IMM, to be installed or removed
by the campaign
**Oct 9 22:07:06 SCALE_SLOT-21 osafsmfnd[2810]: osaf_extended_name.c:144:
osaf_extended_name_length: Assertion 'osaf_extended_names_enabled && length >=
SA_MAX_UNEXTENDED_NAME_LENGTH' failed.**
Oct 9 22:07:06 SCALE_SLOT-21 osafamfnd[2794]: NO
'safSu=SC-1,safSg=NoRed,safApp=OpenSAF' component restart probation timer
started (timeout: 60000000000 ns)
Oct 9 22:07:06 SCALE_SLOT-21 osafamfnd[2794]: NO Restarting a component of
'safSu=SC-1,safSg=NoRed,safApp=OpenSAF' (comp restart count: 1)
Oct 9 22:07:06 SCALE_SLOT-21 osafamfnd[2794]: NO
'safComp=SMFND,safSu=SC-1,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown'
: Recovery is 'componentRestart'
Oct 9 22:07:06 SCALE_SLOT-21 osafsmfnd[3072]: Started
Attachments:
1)Syslog, smf, imm traces of active controller.
---
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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
