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-43766: feat(controller): skip controller name validation #791

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

qJkee
Copy link
Contributor

@qJkee qJkee commented Nov 19, 2024

With new controller runtime kubernetes introduced controller name check. Because of that, graceful restarts started to fail. Because there are no other workaround - we simply disable this check

With new controller runtime kubernetes introduced controller
name check. Because of that, graceful restarts started to fail. Because there are no other workaround - we simply disable this check
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Nov 19, 2024
@openshift-ci-robot
Copy link

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

Requesting review from QA contact:
/cc @mmakwana30

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

In response to this:

With new controller runtime kubernetes introduced controller name check. Because of that, graceful restarts started to fail. Because there are no other workaround - we simply disable this check

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 mmakwana30 November 19, 2024 11:24
@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Nov 19, 2024
Copy link
Contributor

openshift-ci bot commented Nov 19, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qJkee

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 Nov 19, 2024
@codecov-commenter
Copy link

Codecov Report

Attention: Patch coverage is 88.88889% with 1 line in your changes missing coverage. Please review.

Project coverage is 69.01%. Comparing base (267d411) to head (a89e24b).

Files with missing lines Patch % Lines
internal/controllers/vgmanager/controller.go 0.00% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main     #791      +/-   ##
==========================================
- Coverage   69.12%   69.01%   -0.12%     
==========================================
  Files          50       50              
  Lines        3453     3460       +7     
==========================================
+ Hits         2387     2388       +1     
- Misses        879      883       +4     
- Partials      187      189       +2     
Files with missing lines Coverage Δ
...ernal/controllers/lvmcluster/controller_watches.go 75.64% <100.00%> (+0.31%) ⬆️
internal/controllers/node/removal/controller.go 100.00% <100.00%> (ø)
.../controllers/persistent-volume-claim/controller.go 85.52% <100.00%> (+0.19%) ⬆️
...ternal/controllers/persistent-volume/controller.go 100.00% <100.00%> (ø)
internal/controllers/vgmanager/controller.go 71.55% <0.00%> (-0.17%) ⬇️

... and 4 files with indirect coverage changes

---- 🚨 Try these New Features:

@suleymanakbas91
Copy link
Contributor

/lgtm

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

/override "Red Hat Konflux / lvm-operator-on-pull-request"

Copy link
Contributor

openshift-ci bot commented Nov 20, 2024

@suleymanakbas91: Overrode contexts on behalf of suleymanakbas91: Red Hat Konflux / lvm-operator-on-pull-request

In response to this:

/override "Red Hat Konflux / lvm-operator-on-pull-request"

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.

@qJkee
Copy link
Contributor Author

qJkee commented Nov 20, 2024

/test e2e-aws-hypershift

Copy link
Contributor

openshift-ci bot commented Nov 20, 2024

@qJkee: 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.

@qJkee
Copy link
Contributor Author

qJkee commented Nov 20, 2024

/hold

@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 Nov 20, 2024
@openshift-bot
Copy link

/jira refresh

The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.

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

@openshift-bot: This pull request references Jira Issue OCPBUGS-43766, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.18.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Not a Bug) instead

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

The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.

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.

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-important Referenced Jira bug's severity is important 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. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants