Skip to content

OCPBUGS-56878: whereabouts-config is a reserved name for user interaction.#2707

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
dougbtv:fix-whereabouts-configmapname
Jun 5, 2025
Merged

OCPBUGS-56878: whereabouts-config is a reserved name for user interaction.#2707
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
dougbtv:fix-whereabouts-configmapname

Conversation

@dougbtv
Copy link
Copy Markdown
Contributor

@dougbtv dougbtv commented May 13, 2025

In changing to using the flatfile configuration for usage as a configmap, we clobbered the name that we use for allowing overriding the reconciler schedule.

See also: https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/networking/multiple-networks#nw-multus-configuring-whereabouts-ip-reconciler-schedule_configuring-additional-network

@openshift-ci openshift-ci bot requested review from danwinship and jcaamano May 13, 2025 13:21
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 13, 2025
@bpickard22
Copy link
Copy Markdown
Contributor

/retest

@bpickard22
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 28, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented May 28, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bpickard22, dougbtv

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@bpickard22
Copy link
Copy Markdown
Contributor

/retest-required

@bpickard22
Copy link
Copy Markdown
Contributor

/retitle OCPBUGS-56878: whereabouts-config is a reserved name for user interaction.

@openshift-ci openshift-ci bot changed the title whereabouts-config is a reserved name for user interaction. OCPBUGS-56878: whereabouts-config is a reserved name for user interaction. May 29, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels May 29, 2025
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@dougbtv: This pull request references Jira Issue OCPBUGS-56878, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.0) matches configured target version for branch (4.20.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (weliang@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

In changing to using the flatfile configuration for usage as a configmap, we clobbered the name that we use for allowing overriding the reconciler schedule.

See also: https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/networking/multiple-networks#nw-multus-configuring-whereabouts-ip-reconciler-schedule_configuring-additional-network

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.

@bpickard22
Copy link
Copy Markdown
Contributor

/cherry-pick release-4.19

@openshift-cherrypick-robot
Copy link
Copy Markdown

@bpickard22: once the present PR merges, I will cherry-pick it on top of release-4.19 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.19

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.

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD fca1273 and 2 for PR HEAD 0cf7aec in total

1 similar comment
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD fca1273 and 2 for PR HEAD 0cf7aec in total

@bpickard22
Copy link
Copy Markdown
Contributor

/retest-required

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD fca1273 and 2 for PR HEAD 0cf7aec in total

4 similar comments
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD fca1273 and 2 for PR HEAD 0cf7aec in total

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD fca1273 and 2 for PR HEAD 0cf7aec in total

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD fca1273 and 2 for PR HEAD 0cf7aec in total

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD fca1273 and 2 for PR HEAD 0cf7aec in total

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 081ebd8 and 1 for PR HEAD 0cf7aec in total

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 081ebd8 and 2 for PR HEAD 0cf7aec in total

2 similar comments
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 081ebd8 and 2 for PR HEAD 0cf7aec in total

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 081ebd8 and 2 for PR HEAD 0cf7aec in total

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Jun 5, 2025

@dougbtv: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 0cf7aec link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/security 0cf7aec link false /test security
ci/prow/4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade 0cf7aec link false /test 4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade
ci/prow/4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade 0cf7aec link false /test 4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade
ci/prow/4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-upgrade 0cf7aec link false /test 4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-upgrade
ci/prow/e2e-aws-hypershift-ovn-kubevirt 0cf7aec link false /test e2e-aws-hypershift-ovn-kubevirt
ci/prow/e2e-aws-ovn-serial 0cf7aec link false /test e2e-aws-ovn-serial

Full PR test history. Your PR dashboard.

Details

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.

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 081ebd8 and 2 for PR HEAD 0cf7aec in total

@openshift-merge-bot openshift-merge-bot bot merged commit 2bbe72c into openshift:master Jun 5, 2025
31 of 38 checks passed
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@dougbtv: Jira Issue OCPBUGS-56878: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-56878 has been moved to the MODIFIED state.

Details

In response to this:

In changing to using the flatfile configuration for usage as a configmap, we clobbered the name that we use for allowing overriding the reconciler schedule.

See also: https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/networking/multiple-networks#nw-multus-configuring-whereabouts-ip-reconciler-schedule_configuring-additional-network

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-cherrypick-robot
Copy link
Copy Markdown

@bpickard22: new pull request created: #2719

Details

In response to this:

/cherry-pick release-4.19

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.

@openshift-bot
Copy link
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

Distgit: cluster-network-operator
This PR has been included in build cluster-network-operator-container-v4.20.0-202506052341.p0.g2bbe72c.assembly.stream.el9.
All builds following this will include this PR.

@bverschueren
Copy link
Copy Markdown
Contributor

/cherry-pick release-4.18

@openshift-cherrypick-robot
Copy link
Copy Markdown

@bverschueren: new pull request created: #2884

Details

In response to this:

/cherry-pick release-4.18

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants