In an existing discovery job of unix servers I've added code to send node_state attribute values (active / inactive)
In job results vector the value is present:
<object id="47414a53a0161f009e1b909ebab438ea" id_type="CmdbObjectID" class="unix" isReference="false" is_anchor="false">
...
<attribute name="data_externalid" type="String">7886</attribute>
<attribute name="data_note" type="String">Foreman ID: 7886</attribute>
<attribute name="name" type="String">bmitest-elastic1</attribute>
<attribute name="node_state" type="String">active</attribute>
</object>
After running the job, in CMDB the attribute remains empty (not populated) for most of discovered servers, but for some (~10% of them) the value is populated in the node_state attribute
The CI that is getting updated already exists in CMDB with all other attributes and related objects sent in new vector
The only attribute that is different/new in the new vector from job is node_state
What could be the cause for this?
Is there something special with the node_state attribute (used by azure / google cloud discovery jobs)
I am trying to use it in other discovery job, my own code
CMDB / CP 2022.05
Nothing shows up in cmdb.reconciliation.error.log, cmdb.reconciliation.datain.ignored.log, cmdb.reconciliation.datain.merged.log
Please help!