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
Leader election config update. #2282
Conversation
✅ Deploy Preview for hypershift-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
/retest |
/lgtm |
@hasueki: changing LGTM is restricted to collaborators In 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 kubernetes/test-infra repository. |
/retest |
3 similar comments
/retest |
/retest |
/retest |
control-plane-operator/controllers/hostedcontrolplane/kcm/deployment.go
Outdated
Show resolved
Hide resolved
/lgtm |
@muraee |
@cappetersson yeah, I think there was another problem last week. |
@muraee |
@cappetersson we don't have a direct way to check the status of our CI, we have a blocking job on CI stream so you could check the latest release for an indication (e.g. e2e-hypershift is failing here https://amd64.ocp.releases.ci.openshift.org/releasestream/4.14.0-0.ci/release/4.14.0-0.ci-2023-05-29-185629). Actually we have a problem with our CI currently :) |
Oh that is super helpful, thanks for showing me that @muraee! I will keep my eyes on the release page and then re-run the tests when I can see that those problems have been solved:+1: |
/retest |
@muraee |
@cappetersson we need |
/retest |
/retest |
@cappetersson kube-controller-manager logs show this:
The flag should be only |
Ah yes there it is. How were you able to know to look in that specific folder for the logs? Is that just something you know or would I be able to tell based on the information given by the failing tests. |
well if all tests are failing without a clear reason, the first thing I do is to look at the HostedCluster/HostedControlPlane conditions which in this case shows:
so the next step naturally is to check the logs of the failing component. |
/retest |
1 similar comment
/retest |
Finally was able to get all tests to pass. Thanks for all the help on this. |
/lgtm |
/retest |
@muraee |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cappetersson, csrwng 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 |
@cappetersson: 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. |
/cherry-pick release-4.12 |
@cappetersson: new pull request created: #2800 In 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 kubernetes/test-infra repository. |
/cherry-pick release-4.13 |
/cherry-pick release-4.14 |
/cherry-pick release-4.15 |
@cappetersson: new pull request created: #2801 In 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 kubernetes/test-infra repository. |
@cappetersson: new pull request could not be created: failed to create pull request against openshift/hypershift#release-4.14 from head openshift-cherrypick-robot:cherry-pick-2282-to-release-4.14: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between openshift:release-4.14 and openshift-cherrypick-robot:cherry-pick-2282-to-release-4.14"}],"documentation_url":"https://docs.github.com/rest/reference/pulls#create-a-pull-request"} In 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 kubernetes/test-infra repository. |
@cappetersson: new pull request could not be created: failed to create pull request against openshift/hypershift#release-4.15 from head openshift-cherrypick-robot:cherry-pick-2282-to-release-4.15: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between openshift:release-4.15 and openshift-cherrypick-robot:cherry-pick-2282-to-release-4.15"}],"documentation_url":"https://docs.github.com/rest/reference/pulls#create-a-pull-request"} In 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 kubernetes/test-infra repository. |
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use
fixes #<issue_number>(, fixes #<issue_number>, ...)
format, where issue_number might be a GitHub issue, or a Jira story:Fixes #1391
Checklist