-
Notifications
You must be signed in to change notification settings - Fork 463
[release-4.19] OCPBUGS-64922: Update timing of MCN desired config spec update to align with node annotation setting #5439
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
Conversation
|
@isabella-janssen: This pull request references Jira Issue OCPBUGS-64922, which is valid. 7 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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. |
|
/test unit |
|
Pre-merge tested: Environment Setup Steps:
MC Template$ oc create -f - << EOF
apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
metadata:
labels:
machineconfiguration.openshift.io/role: worker
name: test-file
spec:
config:
ignition:
version: 3.4.0
storage:
files:
- contents:
source: data:text/plain;charset=utf-8;base64,dGVzdA==
filesystem: root
mode: 420
path: /etc/test-file.test
EOF
machineconfig.machineconfiguration.openshift.io/test-file created
$ oc describe machineconfignode ip-10-0-72-244.ec2.internal | grep -E "Config Version|UpdatePrepared" -A 2
Config Version:
Desired: rendered-worker-e0be4e6d0110c62a60651bf9764d3304
Node:
--
Reason: UpdatePrepared
Status: True
Type: UpdatePrepared
Last Transition Time: 2025-11-25T09:30:37Z
Message: Updated the Files and OS on disk as a part of the in progress phase
--
Config Version:
Current: rendered-worker-4d4f56422c551acab421a91c38dfae93
Desired: rendered-worker-e0be4e6d0110c62a60651bf9764d3304
- After Update
oc describe machineconfignode ip-10-0-72-244.ec2.internal | grep -E "Config Version|UpdatePrepared" -A 2
Config Version:
Desired: rendered-worker-e0be4e6d0110c62a60651bf9764d3304
Node:
--
Reason: UpdatePrepared
Status: False
Type: UpdatePrepared
Last Transition Time: 2025-11-25T09:31:45Z
Message: Action during update to rendered-worker-e0be4e6d0110c62a60651bf9764d3304: Updated the Files and OS on disk as a part of the in progress phase
--
Config Version:
Current: rendered-worker-e0be4e6d0110c62a60651bf9764d3304
Desired: rendered-worker-e0be4e6d0110c62a60651bf9764d3304
- Able to see the status.configVersion.desired updated as soon as spec.configVersion.desired is updated.
/verified by @ptalgulk01 |
|
@isabella-janssen: This pull request references Jira Issue OCPBUGS-64922, which is valid. 7 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn 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. |
|
@ptalgulk01: This PR has been marked as verified by DetailsIn 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. |
|
/lgtm /label backport-risk-assessed |
|
hmm actually, it seems like the units constructor calls might need some tweaking as well 😓 |
|
/test unit Units seem to be passing on my end, so I'm trying them again here. |
|
/test unit |
1 similar comment
|
/test unit |
|
@isabella-janssen: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
…e to node controller to align with annotation setting timing
c77dd73 to
f009b5e
Compare
|
/test unit Units are passing locally :( |
|
/verified by @ptalgulk01 See verification here. The only change since that verification was a minor fix to the unit tests, which does not impact the added functionality. |
|
@isabella-janssen: This PR has been marked as verified by DetailsIn 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. |
|
/payload-job periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial Just double checking that this change doesn't push any thresholds over their limits in the blocking suites with MCN tests. |
|
@isabella-janssen: trigger 2 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c282dc90-cadb-11f0-9022-bebc93c5d505-0 |
|
/lgtm /label backport-risk-assessed |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: djoshy, isabella-janssen The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
6fd31b7
into
openshift:release-4.19
|
@isabella-janssen: Jira Issue Verification Checks: Jira Issue OCPBUGS-64922 Jira Issue OCPBUGS-64922 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 DetailsIn 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. |
This is a manual cherry-pick of #5367 because the automated cherry-pick was resulting in build failures in the CI test runs.