#2580 log: fail to start log server when running with old IMM model

[Vu Minh Nguyen]

LOG introduced the saLogRecordDestination attribute since OpenSAF 5.2 to handle the alternative destinations of log records, ticket [#2258].

During upgrade, if LOG server comes up before IMM model is updated to new one which has saLogRecordDestination in, LOG server will be crashed.

[Vu Minh Nguyen]

commit 095b3e7d71f57c8931e99a9b9143b67afde85134 (HEAD, origin/develop, develop)
Author: Vu Minh Nguyen vu.m.nguyen@dektech.com.au
Date: Fri Sep 15 09:33:58 2017 +0700

log: fix log server fail to start with old IMM model [#2580]

LOG introduced the `saLogRecordDestination` attribute since OpenSAF 5.2
to handle the alternative destinations of log records, ticket [#2258].
During upgrade, if LOG server comes up before IMM model is updated
to new one which has saLogRecordDestination in, LOG server will be crashed

The solution is getting all attributes from running IMM model using
saImmOmClassDescriptionGet(). Only fetching values of non-pure attributes.
If not having newly added attribute, use default ones.

commit c88ba32e0e958920c91a8b52825fd3b757f7c985 (HEAD, origin/release, release)
Author: Vu Minh Nguyen vu.m.nguyen@dektech.com.au
Date: Fri Sep 15 09:33:58 2017 +0700

log: fix log server fail to start with old IMM model [#2580]

LOG introduced the `saLogRecordDestination` attribute since OpenSAF 5.2
to handle the alternative destinations of log records, ticket [#2258].
During upgrade, if LOG server comes up before IMM model is updated
to new one which has saLogRecordDestination in, LOG server will be crashed

The solution is getting all attributes from running IMM model using
saImmOmClassDescriptionGet(). Only fetching values of non-pure attributes.
If not having newly added attribute, use default ones.