Container health checks spam the logs

[wezell]

Parent Issue

No response

Problem Statement

Our container health checks all resolve to IPv6 addresses, which our IPUtils cannot parse. This throws repeated errors in the logs, basically spamming them. We need to set IPUtils to ignore IPv6 addresses.

Steps to Reproduce

[19/07/24 18:34:02:646 GMT]  WARN network.IPUtils: Could not parse [0:0:0:0:0:0:0:1]
[19/07/24 18:34:02:646 GMT]  WARN network.IPUtils: com.dotcms.repackage.org.apache.commons.net.util.SubnetUtils.toInteger(SubnetUtils.java:252)
[19/07/24 18:34:12:656 GMT]  WARN network.IPUtils: subnet:0.0.0.0/1, ip:0:0:0:0:0:0:0:1, error:Could not parse [0:0:0:0:0:0:0:1]
[19/07/24 18:34:12:656 GMT]  WARN network.IPUtils: Could not parse [0:0:0:0:0:0:0:1]
[19/07/24 18:34:12:657 GMT]  WARN network.IPUtils: com.dotcms.repackage.org.apache.commons.net.util.SubnetUtils.toInteger(SubnetUtils.java:252)
[19/07/24 18:34:22:667 GMT]  WARN network.IPUtils: subnet:0.0.0.0/1, ip:0:0:0:0:0:0:0:1, error:Could not parse [0:0:0:0:0:0:0:1]
[19/07/24 18:34:22:667 GMT]  WARN network.IPUtils: subnet:0.0.0.0/1, ip:0:0:0:0:0:0:0:1, error:Could not parse [0:0:0:0:0:0:0:1]
[19/07/24 18:34:22:667 GMT]  WARN network.IPUtils: Could not parse [0:0:0:0:0:0:0:1]
[19/07/24 18:34:22:667 GMT]  WARN network.IPUtils: Could not parse [0:0:0:0:0:0:0:1]
[19/07/24 18:34:22:667 GMT]  WARN network.IPUtils: com.dotcms.repackage.org.apache.commons.net.util.SubnetUtils.toInteger(SubnetUtils.java:252)

[19/07/24 18:34:22:667 GMT]  WARN network.IPUtils: com.dotcms.repackage.org.apache.commons.net.util.SubnetUtils.toInteger(SubnetUtils.java:252)
[19/07/24 18:34:32:646 GMT]  WARN network.IPUtils: subnet:0.0.0.0/1, ip:0:0:0:0:0:0:0:1, error:Could not parse [0:0:0:0:0:0:0:1]
[19/07/24 18:34:32:646 GMT]  WARN network.IPUtils: Could not parse [0:0:0:0:0:0:0:1]
[19/07/24 18:34:32:646 GMT]  WARN network.IPUtils: com.dotcms.repackage.org.apache.commons.net.util.SubnetUtils.toInteger(SubnetUtils.java:252)
[19/07/24 18:34:42:636 GMT]  WARN network.IPUtils: subnet:0.0.0.0/1, ip:0:0:0:0:0:0:0:1, error:Could not parse [0:0:0:0:0:0:0:1]
[19/07/24 18:34:42:636 GMT]  WARN network.IPUtils: Could not parse [0:0:0:0:0:0:0:1]
[19/07/24 18:34:42:636 GMT]  WARN network.IPUtils: com.dotcms.repackage.org.apache.commons.net.util.SubnetUtils.toInteger(SubnetUtils.java:252)
[19/07/24 18:34:52:646 GMT]  WARN network.IPUtils: subnet:0.0.0.0/1, ip:0:0:0:0:0:0:0:1, error:Could not parse [0:0:0:0:0:0:0:1]
[19/07/24 18:34:52:646 GMT]  WARN network.IPUtils: subnet:0.0.0.0/1, ip:0:0:0:0:0:0:0:1, error:Could not parse [0:0:0:0:0:0:0:1]
[19/07/24 18:34:52:646 GMT]  WARN network.IPUtils: Could not parse [0:0:0:0:0:0:0:1]
[19/07/24 18:34:52:646 GMT]  WARN network.IPUtils: Could not parse [0:0:0:0:0:0:0:1]
[19/07/24 18:34:52:646 GMT]  WARN network.IPUtils: com.dotcms.repackage.org.apache.commons.net.util.SubnetUtils.toInteger(SubnetUtils.java:252)
[19/07/24 18:34:52:646 GMT]  WARN network.IPUtils: com.dotcms.repackage.org.apache.commons.net.util.SubnetUtils.toInteger(SubnetUtils.java:252)

Acceptance Criteria

Return true if the address resolves to IPv6 as we cannot parse those. We should spit out a warning message to the log every 10m.

dotCMS Version

Proposed Objective

Cloud Engineering

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response