#1474 imm: Assigning default value to no-dangling attributes make cluster fail to start

[Hung Nguyen]

root@SC1:~# immlist -c Test
<< Test - CONFIG >>
test : SA_STRING_T [1] {RDN, CONFIG, INITIALIZED}
dep : SA_NAME_T [0] = test=1 (6) {CONFIG, WRITEABLE, NO_DANGLING}

Create test=1 and test=2
root@SC1:~# immcfg -c Test test=1
root@SC1:~# immcfg -c Test test=2

Set the attribute with default value to empty.
root@SC1:~# immcfg -a dep= test=2
root@SC-1:~# immlist -a dep test=2
dep=<Empty>

Now test=1 can be deleted
root@SC1:~# immcfg -d test=1

Reboot cluster and it will fail to start
Sep 10 21:03:36 SC1 osafimmloadd: NO ** Loading from PBE file imm.db at /srv/shared/imm/ **
Sep 10 21:03:40 SC1 osafimmnd[421]: NO ERR_FAILED_OPERATION: NO_DANGLING reference (test=1) is dangling (Ccb 1)
Sep 10 21:03:40 SC1 osafimmnd[421]: NO Ccb 1 ABORTED (IMMLOADER)

[#1377]

[Anders Bjornerstedt]

Raising severity to critical since the symptom caused by this defect is severe.

I propose that the solution is to not allow default values to be defined for attributes flagged with NO_DANGLING in the class definition.

[Zoran Milinkovic]

opensaf-4.5.x:

changeset: 6850:14d148411636
branch: opensaf-4.5.x
parent: 6847:521b2c5b866c
user: Hung Nguyen hung.d.nguyen@dektech.com.au
date: Wed Sep 16 15:32:27 2015 +0700
summary: imm: Don't allow default values to be defined with NO_DANGLING flag when creating classes [#1474]

---

opensaf-4.6.x:

changeset: 6851:b0b8ac13e307
branch: opensaf-4.6.x
parent: 6848:f3e9ebe80cd1
user: Hung Nguyen hung.d.nguyen@dektech.com.au
date: Wed Sep 16 15:32:27 2015 +0700
summary: imm: Don't allow default values to be defined with NO_DANGLING flag when creating classes [#1474]

---

default(4.7):

changeset: 6852:c2cb70c2e0d6
tag: tip
parent: 6849:68ea2b13deca
user: Hung Nguyen hung.d.nguyen@dektech.com.au
date: Wed Sep 16 15:32:27 2015 +0700
summary: imm: Don't allow default values to be defined with NO_DANGLING flag when creating classes [#1474]