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

OCPBUGS-16547: Bump machine-config-operator #966

Merged

Conversation

SalDaniele
Copy link
Contributor

Update machine config operator to remove dependency on goproxy.

Signed-off-by: Salvatore Daniele <[email protected]>
Signed-off-by: Salvatore Daniele <[email protected]>
Due to updating the machine config operator, we removed an indirect
dependency on github.com/golang/glog. This package provides an init()
method which sets a number of flags that we expect to be present [1].

To ensure compatability with the updates, we can explicitly add these
flags with the klog.init() method [2]. It is better to include packages
that are required to keep the API consistent explicitly.

[1] https://github.com/golang/glog/blob/424d2337a5299a465c8a8228fc3ba4b1c28337a2/glog.go#L398-L404
[2]
https://github.com/kubernetes/klog#:~:text=Use%20klog.InitFlags(nil)%20explicitly%20for%20initializing%20global%20flags%20as%20we%20no%20longer%20use%20init()%20method%20to%20register%20the%20flags

Signed-off-by: Salvatore Daniele <[email protected]>
@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 Jul 16, 2024
@openshift-ci-robot
Copy link
Contributor

@SalDaniele: This pull request references Jira Issue OCPBUGS-16547, which is invalid:

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:

Backport of k8snetworkplumbingwg/sriov-network-operator#707

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.

@SalDaniele
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@SalDaniele: This pull request references Jira Issue OCPBUGS-16547, which is invalid:

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.

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.

@SalDaniele
Copy link
Contributor Author

/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 Jul 16, 2024
@openshift-ci-robot
Copy link
Contributor

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-36335 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-36335 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0, 4.15.z
  • bug has dependents

Requesting review from QA contact:
/cc @zhaozhanqi

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 review from zhaozhanqi, Billy99 and dougbtv July 16, 2024 13:53
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 16, 2024
@SalDaniele
Copy link
Contributor Author

/retest ci/prow/security

Copy link
Contributor

openshift-ci bot commented Jul 16, 2024

@SalDaniele: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test api
  • /test ci-index-sriov-network-operator-bundle
  • /test controllers
  • /test gofmt
  • /test images
  • /test operator-e2e
  • /test pkg

The following commands are available to trigger optional jobs:

  • /test e2e-openstack-nfv
  • /test e2e-openstack-nfv-hwoffload

Use /test all to run all jobs.

In response to this:

/retest ci/prow/security

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.

@SalDaniele
Copy link
Contributor Author

/test ci/prow/security

Copy link
Contributor

openshift-ci bot commented Jul 16, 2024

@SalDaniele: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test api
  • /test ci-index-sriov-network-operator-bundle
  • /test controllers
  • /test gofmt
  • /test images
  • /test operator-e2e
  • /test pkg

The following commands are available to trigger optional jobs:

  • /test e2e-openstack-nfv
  • /test e2e-openstack-nfv-hwoffload

Use /test all to run all jobs.

In response to this:

/test ci/prow/security

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.

@SalDaniele
Copy link
Contributor Author

@zeeke PTAL, last one :)

@SalDaniele
Copy link
Contributor Author

/retest

@zeeke
Copy link
Contributor

zeeke commented Jul 29, 2024

/lgtm
/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jul 29, 2024
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 29, 2024
Copy link
Contributor

openshift-ci bot commented Jul 29, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SalDaniele, zeeke

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

@SalDaniele
Copy link
Contributor Author

@zhaozhanqi @yingwang-0320 PTAL

@zhaozhanqi
Copy link

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jul 29, 2024
@SalDaniele
Copy link
Contributor Author

/override ci/prow/security

Copy link
Contributor

openshift-ci bot commented Jul 29, 2024

@SalDaniele: Overrode contexts on behalf of SalDaniele: ci/prow/security

In response to this:

/override ci/prow/security

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.

Copy link
Contributor

openshift-ci bot commented Jul 29, 2024

@SalDaniele: 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-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 96c2605 into openshift:release-4.14 Jul 29, 2024
11 checks passed
@openshift-ci-robot
Copy link
Contributor

@SalDaniele: Jira Issue OCPBUGS-16547: All pull requests linked via external trackers have merged:

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

In response to this:

Backport of k8snetworkplumbingwg/sriov-network-operator#707

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

[ART PR BUILD NOTIFIER]

Distgit: sriov-network-config-daemon
This PR has been included in build sriov-network-config-daemon-container-v4.14.0-202407291940.p0.g96c2605.assembly.stream.el8.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: sriov-network-webhook
This PR has been included in build sriov-network-webhook-container-v4.14.0-202407292140.p0.g96c2605.assembly.stream.el8.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: sriov-network-operator
This PR has been included in build sriov-network-operator-container-v4.14.0-202407292140.p0.g96c2605.assembly.stream.el8.
All builds following this will include this PR.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.