Skip to content
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

NO-JIRA: HyperShift code linter PR837 followup #910

Merged
merged 1 commit into from Jan 16, 2024

Conversation

jmencak
Copy link
Contributor

@jmencak jmencak commented Jan 9, 2024

#456 introduced support for MachineConfig-like functionality for HyperShift via NTO. This PR unnecessarily creates a runtime.Scheme on every invocation of getMachineConfigFromConfigMap() and serializeMachineConfig() function as pointed out in #837 (comment). Make the scheme an attribute of the controller and initialize it only once at controller instantiation.

/cc

PR456 introduced support for MachineConfig-like functionality for
HyperShift via NTO.  This PR unnecessarily creates a runtime.Scheme on
every invocation of getMachineConfigFromConfigMap() and
serializeMachineConfig() function as pointed out in PR837.  Make the
scheme an attribute of the controller and initialize it only once at
controller instantiation.
Copy link
Contributor

openshift-ci bot commented Jan 9, 2024

@jmencak: GitHub didn't allow me to request PR reviews from the following users: jmencak.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

#456 introduced support for MachineConfig-like functionality for HyperShift via NTO. This PR unnecessarily creates a runtime.Scheme on every invocation of getMachineConfigFromConfigMap() and serializeMachineConfig() function as pointed out in #837 (comment). Make the scheme an attribute of the controller and initialize it only once at controller instantiation.

/cc

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.

Copy link
Contributor

openshift-ci bot commented Jan 9, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jmencak

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 9, 2024
@jmencak
Copy link
Contributor Author

jmencak commented Jan 9, 2024

/cc @dagrayvid
/cc @ffromani
Francesco, hope this is the direction you wanted the issues in #837 (comment) resolved.

I have not tested this manually in HyperShift, as it can be quite time consuming. I believe this should be covered by the ci/prow/e2e-hypershift. @dagrayvid , please keep me honest here.

Copy link
Contributor

@ffromani ffromani left a comment

Choose a reason for hiding this comment

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

thanks @jmencak this change indeed addresses my suggestion.
non-binding LGTM till we are sure the code is covered by tests (and only because we're not sure and checking)

@dagrayvid
Copy link
Contributor

@jmencak Yes that is right. I also checked the logs of the e2e-hypershift test to confirm:

        --- PASS: TestNodePool/Main/TestNTOMachineConfigGetsRolledOut (1315.21s)
            --- PASS: TestNodePool/Main/TestNTOMachineConfigGetsRolledOut/EnsureNoCrashingPods (0.02s)
            --- PASS: TestNodePool/Main/TestNTOMachineConfigGetsRolledOut/EnsureAllContainersHavePullPolicyIfNotPresent (0.01s)
            --- PASS: TestNodePool/Main/TestNTOMachineConfigGetsRolledOut/EnsureHCPContainersHaveResourceRequests (0.01s)
            --- PASS: TestNodePool/Main/TestNTOMachineConfigGetsRolledOut/EnsureNoPodsWithTooHighPriority (0.02s)

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 9, 2024
@dagrayvid
Copy link
Contributor

/retest-required

@jmencak
Copy link
Contributor Author

jmencak commented Jan 10, 2024

/retest

1 similar comment
@jmencak
Copy link
Contributor Author

jmencak commented Jan 10, 2024

/retest

@jmencak jmencak changed the title HyperShift code linter PR837 followup NO-JIRA: HyperShift code linter PR837 followup Jan 10, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 10, 2024
@openshift-ci-robot
Copy link
Contributor

@jmencak: This pull request explicitly references no jira issue.

In response to this:

#456 introduced support for MachineConfig-like functionality for HyperShift via NTO. This PR unnecessarily creates a runtime.Scheme on every invocation of getMachineConfigFromConfigMap() and serializeMachineConfig() function as pointed out in #837 (comment). Make the scheme an attribute of the controller and initialize it only once at controller instantiation.

/cc

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-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 7820510 and 2 for PR HEAD 0de6589 in total

@jmencak
Copy link
Contributor Author

jmencak commented Jan 10, 2024

ci/prow/e2e-gcp-pao-updating-profile issues likely caused by https://issues.redhat.com/browse/OCPBUGS-26589

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD cff2950 and 1 for PR HEAD 0de6589 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD dfc37fc and 0 for PR HEAD 0de6589 in total

@jmencak
Copy link
Contributor Author

jmencak commented Jan 16, 2024

/retest

@openshift-ci-robot
Copy link
Contributor

/hold

Revision 0de6589 was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 16, 2024
@jmencak
Copy link
Contributor Author

jmencak commented Jan 16, 2024

/hold cancel
/retest

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 16, 2024
Copy link
Contributor

openshift-ci bot commented Jan 16, 2024

@jmencak: 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/test-infra repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit f2f453f into openshift:master Jan 16, 2024
15 checks passed
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build cluster-node-tuning-operator-container-v4.16.0-202401162251.p0.gf2f453f.assembly.stream for distgit cluster-node-tuning-operator.
All builds following this will include this PR.

@jmencak jmencak deleted the 4.16-PR837-followup branch January 17, 2024 07:12
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-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.

None yet

5 participants