ACC Linux host data collection selects first routable IPv4 instead of default-gateway interface IP for CI ip_address on multi-homed hostsDescriptionOn multi-homed Linux hosts discovered through ACC Collect Host Data, the Linux host data collection logic populates basic_inventory.ip_address by selecting the first routable IPv4 returned from OSQuery interface enumeration.Because this logic does not prefer the interface associated with the default gateway, the CI ip_address can be populated with a private/interconnect NIC IP instead of the production/routed IP.This is separate from PRB1782194, which addressed the keepalive or agent record IP path. The CI ip_address path in data_collection.rb still follows first-valid-IPv4 selection logic and does not use default gateway preference.Steps to Reproduce 1. Use a Linux host with multiple NICs where:- a private/interconnect IPv4 interface is enumerated before the production interface- the production interface has the valid default gateway used to reach the MID server2. Install and connect ACC on the host.3. Run Collect Host Data from the agent record.4. Review the payload and resulting CI update.5. Observe that:- network adapters include the correct production interface and gateway details- basic_inventory.ip_address is selected from the first routable IPv4 returned by OSQuery- cmdb_ci_linux_server.ip_address is populated with the earlier private/interconnect IP instead of the routed production IPExpected result:CI ip_address should prefer the IP from the interface associated with the valid default gateway or routed transport path, not simply the first routable IPv4 returned by interface enumeration.WorkaroundThis problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.Related Problem: PRB2007957