This behaviour is non backwards compatible. I must be possible to enable in a
campaign.
>From SMF PR document:
"4.5.7 Enabling long DN support from a campaign
When enabling long DN support from a campaign, the CCB containing the IMM
configuration change must be defined in the <campaignInitialization> portion.
The long DN support can then be used in subsequent CCB's."
Tests for enabling as above worked before the change but now they fail
---
** [tickets:#2119] smf: Long DN setting in IMM is not correctly detected**
**Status:** assigned
**Milestone:** 5.0.2
**Created:** Thu Oct 13, 2016 03:07 PM UTC by elunlen
**Last Updated:** Fri Oct 14, 2016 02:37 PM UTC
**Owner:** Neelakanta Reddy
**Attachments:**
-
[long_dn_campaign.xml](https://sourceforge.net/p/opensaf/tickets/2119/attachment/long_dn_campaign.xml)
(22.8 kB; text/xml)
-
[osafsmfd](https://sourceforge.net/p/opensaf/tickets/2119/attachment/osafsmfd)
(251.3 kB; application/octet-stream)
- [syslog](https://sourceforge.net/p/opensaf/tickets/2119/attachment/syslog)
(31.9 kB; application/octet-stream)
After ticket SMF: smfnd asserted on active controller with long dn when
executing the campaign [#2087] was fixed long DN settings in IMM is no longer
read correctly. Campaigns with long DN fail.
Attached: Campaign, syslog and osafsmfd trace
---
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
