Rudder

In some configuration, a server may have two interface with the same IP, for example:

eth0      Link encap:Ethernet  HWaddr 78:E7:D1:F6:F9:14
          inet addr:10.0.0.1  Bcast:10.0.0.255  Mask:255.255.255.0
          ....

eth1      Link encap:Ethernet  HWaddr 78:E7:D1:F6:F9:14
          inet addr:10.0.0.1  Bcast:10.0.0.255  Mask:255.255.255.0
          ....

That leads to a "duplicate attribute valie" error in LDAP, like:

[2013-05-27 16:01:11] INFO  com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - New input report: 'xxxx-2013-05-27-13-19-31.ocs'
[2013-05-27 16:01:12] INFO  com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Report 'xxxx-2013-05-27-13-19-31.ocs' parsed in 493 milliseconds, sending to save engine.
[2013-05-27 16:01:13] ERROR com.normation.ldap.sdk.RwLDAPConnection - Exception ignored (by configuration) when trying to add entry 'nodeId=44446623-a36a-429a-8b19-bdf6fc250ae3,ou=Nodes,ou=Pending Inventories,ou=Inventories,cn=rudder-configuration'.  
Reported exception was: ipHostNumber: value #2 provided more than once

com.unboundid.ldap.sdk.LDAPException: ipHostNumber: value #2 provided more than once
        at com.unboundid.ldap.sdk.LDAPConnection.add(LDAPConnection.java:1648) ~[unboundid-ldapsdk-2.3.1.jar:2.3.1]

The problem (that we don't have for mac address) is that we summurize all ips in the Node entry, and in that case, we have a duplicate one.
Solution: just add distinct IP, we don't loose any information.