New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCPBUGS-18396: Fix config status MTU migration not being updated #2021
Conversation
cc @kyrtapz |
Render has side effects in the passed in operConfig that are reflected later on in the status when it is being updated. This stopped working when the the passed in operConfig was changed to a copy that was not then used when applying the status. It makes sense to use the updated operConfig for everything that comes after, not just Render, so change that to fix the issue. Fixes: openshift#1952 Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
/hold |
/retest |
1 similar comment
/retest |
/retitle OCPBUGS-18396: Fix config status MTU migration not being updated |
@jcaamano: This pull request references Jira Issue OCPBUGS-18396, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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 kubernetes/test-infra repository. |
/retest |
/lgtm |
/test e2e-network-mtu-migration-ovn-ipv6 |
ci/prow/e2e-network-mtu-migration-ovn-ipv6 seems to be fine, it failed on a final test data collection that has also been oberseved to fail in the normal ipv6 job: |
/test e2e-network-mtu-migration-ovn-ipv6 |
/jira refresh |
@trozet: This pull request references Jira Issue OCPBUGS-18396, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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 kubernetes/test-infra repository. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jcaamano, kyrtapz, trozet 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 |
/hold cancel |
@jcaamano: The following tests failed, say
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/test-infra repository. I understand the commands that are listed here. |
2b544dd
into
openshift:master
@jcaamano: Jira Issue OCPBUGS-18396: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-18396 has been moved to the MODIFIED state. 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 kubernetes/test-infra repository. |
/cherry-pick release-4.14 |
@jcaamano: new pull request created: #2034 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 kubernetes/test-infra repository. |
Fix included in accepted release 4.15.0-0.nightly-2023-09-27-073353 |
Render has side effects in the passed in operConfig that are reflected later on in the status when it is being updated. This stopped working when the the passed in operConfig was changed to a copy that was not then used when applying the status.
It makes sense to use the updated operConfig for everything that comes after, not just Render, so change that to fix the issue.
Fixes: #1952