USHIFT-3177: Use only ipv4 addresses for default router #3407
Conversation
There was a mismatch between what the config package IP addresses from the host and the router controller. The config package only gets ipv4 addresses while the router controller takes ipv6 too. This caused a mismatch between allowed/configured IP addresses that triggered fake warning logs about ipv6 entries not allowed in the service (even if they were not configured).
openshift-ci-robot
added
the
jira/valid-reference
|
@pacevedom: This pull request references USHIFT-3177 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target either version "4.17." or "openshift-4.17.", but it targets "openshift-4.16" instead. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
added
the
approved
|
@pacevedom: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ggiguash, pacevedom The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a mismatch between what the config package IP addresses from the host and the router controller. The config package only gets ipv4 addresses while the router controller takes ipv6 too. This caused a mismatch between allowed/configured IP addresses that triggered fake warning logs about ipv6 entries not allowed in the service (even if they were not configured).
Which issue(s) this PR addresses:
Closes #