This is a clone of issue OCPBUGS-60112. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-60111. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-60110. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-55971. The following is the description of the original issue:
—
Description of problem:

At some point we significantly reduced the amount of logging from the runtimecfg node ip commands because it was spamming the keepalived logs. However, this also resulted in us losing the additional logging for the nodeip-configuration service where we do still want it. There is a way to enable debug logging via a config-map, but I'm not clear whether that would work very early in the deployment process when a lot of nodeip-configuration issues happen. It would also be nice to just have those logs available so we don't have to go back and forth with customers to get the necessary information. Since nodeip-configuration only runs once per boot the extra messages aren't really a problem.

We may want to re-enable the behavior in https://github.com/openshift/baremetal-runtimecfg/commit/0561ac232cd8c56913173fd14fb855376bcbbaf8 so that we can turn this on just for nodeip-configuration, but I want to discuss with Mat first.

Version-Release number of selected component (if applicable):

    4.16 appears to be when these changes were made

How reproducible:

    Always

Steps to Reproduce:

    1. Deploy cluster
    2. Look at nodeip-configuration logs on a node
    3.
    

Actual results:

    Minimal information

Expected results:

    Full details of IP and route information available at the time.

Additional info: