Skip to content

Conversation

sdodson
Copy link
Member

@sdodson sdodson commented Sep 30, 2025

Prior to this we're emitting the event everytime the config is built even though we're not applying it.

Fixes: OCPBUGS-62493

- What I did
Moved the event and metrics update code to the bit of code that creates the new config if it's missing.

- How to verify it
set osImageURL and see if events are emitted each time the config is reconciled

- Description for the changelog
Emit OSImageURLOverridden only when creating a new config

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 30, 2025
@openshift-ci-robot
Copy link
Contributor

@sdodson: This pull request references Jira Issue OCPBUGS-62493, which is invalid:

  • expected the bug to target the "4.21.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

In response to this:

Prior to this we're emitting the event everytime the config is built even though we're not applying it.

Fixes: OCPBUGS-62493

- What I did
Moved the event and metrics update code to the bit of code that creates the new config if it's missing.

- How to verify it
set osImageURL and see if events are emitted each time the config is reconciled

- Description for the changelog
Emit OSImageURLOverridden only when creating a new config

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.

Comment on lines 575 to 578
} else {
// Reset metric when OSImageURL has not been overridden
ctrlcommon.OSImageURLOverride.WithLabelValues(pool.Name).Set(0)
}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe the metrics bits should be moved out of this portion of code so that if the controller is restarted they're always accurate?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That could work, probably check if the existing metric is already at 0/1 and only re-event if that changes? (Although I don't think that's the right way to do event metrics, as far as I understand it)

if err != nil {
return err
}
// Emit event and collect metric when OSImageURL was overridden and we're going to apply a new config
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// Emit event and collect metric when OSImageURL was overridden and we're going to apply a new config
// Emit event and collect metric when OSImageURL was overridden and we're going to create a new config

maybe?

Copy link
Contributor

openshift-ci bot commented Sep 30, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sdodson
Once this PR has been reviewed and has the lgtm label, please assign rishabhsaini for approval. For more information see the Code Review Process.

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

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

@sdodson
Copy link
Member Author

sdodson commented Sep 30, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 30, 2025
@openshift-ci-robot
Copy link
Contributor

@sdodson: This pull request references Jira Issue OCPBUGS-62493, 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.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sergiordlr

In response to this:

/jira refresh

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 openshift-ci bot requested a review from sergiordlr September 30, 2025 18:12
Copy link
Contributor

@yuqi-zhang yuqi-zhang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

generally looks fine, some discussion inline

ctrl.eventRecorder.Eventf(generated, corev1.EventTypeNormal, "OSImageURLOverridden", "OSImageURL was overridden via machineconfig in %s (was: %s is: %s)", generated.Name, cc.Spec.OSImageURL, generated.Spec.OSImageURL)
} else {
// Reset metric when OSImageURL has not been overridden
ctrlcommon.OSImageURLOverride.WithLabelValues(pool.Name).Set(0)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the reset here should probably live outside of this block, since the metric will stay at (1) if you delete the config in this workflow (and revert back to the old config)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where's that happening? I'm not seeing an obvious place where we do that :(

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rather I think it probably makes more sense to have the metrics and eventing be separate processes, so the event only gets fired on changes, but we can keep the metric setting outside

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I've updated it to achieve that now.

Comment on lines 575 to 578
} else {
// Reset metric when OSImageURL has not been overridden
ctrlcommon.OSImageURLOverride.WithLabelValues(pool.Name).Set(0)
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That could work, probably check if the existing metric is already at 0/1 and only re-event if that changes? (Although I don't think that's the right way to do event metrics, as far as I understand it)

Prior to this we're emitting the event everytime the config is built
even though we're not applying it.
Copy link
Contributor

openshift-ci bot commented Oct 2, 2025

@sdodson: 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/okd-scos-e2e-aws-ovn 8988ae4 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-gcp-mco-disruptive 8988ae4 link false /test e2e-gcp-mco-disruptive
ci/prow/e2e-gcp-op-ocl 8988ae4 link false /test e2e-gcp-op-ocl
ci/prow/e2e-azure-ovn-upgrade-out-of-change 8988ae4 link false /test e2e-azure-ovn-upgrade-out-of-change
ci/prow/e2e-aws-mco-disruptive 8988ae4 link false /test e2e-aws-mco-disruptive
ci/prow/bootstrap-unit 8988ae4 link false /test bootstrap-unit

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.

@sdodson
Copy link
Member Author

sdodson commented Oct 3, 2025

/retest-required

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants