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.

Sign up for GitHub

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

Jump to bottom

[release-4.10] Bug 2043806: UPSTREAM 107564: kube-apiserver integration test: allow IPs with leading zeros on the API #1133

Merged
merged 1 commit into from Feb 4, 2022
Merged

[release-4.10] Bug 2043806: UPSTREAM 107564: kube-apiserver integration test: allow IPs with leading zeros on the API #1133

merged 1 commit into from Feb 4, 2022

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #1124

/assign aojea

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jan 22, 2022
Merged
@openshift-ci-robot openshift-ci-robot added the backports/validated-commits Indicates that all commits come to merged upstream PRs. label Jan 22, 2022
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: the contents of this pull request could be automatically validated.

The following commits are valid:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci
Copy link

openshift-ci bot commented Jan 22, 2022

@openshift-cherrypick-robot: Bugzilla bug 2042493 has been cloned as Bugzilla bug 2043806. Retitling PR to link against new bug.
/retitle [release-4.10] Bug 2043806: UPSTREAM 107564: kube-apiserver integration test: allow IPs with leading zeros on the API

In response to this:

[release-4.10] Bug 2042493: UPSTREAM 107564: kube-apiserver integration test: allow IPs with leading zeros on the API

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.

@openshift-ci openshift-ci bot changed the title [release-4.10] Bug 2042493: UPSTREAM 107564: kube-apiserver integration test: allow IPs with leading zeros on the API [release-4.10] Bug 2043806: UPSTREAM 107564: kube-apiserver integration test: allow IPs with leading zeros on the API Jan 22, 2022
@openshift-ci openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Jan 22, 2022
@openshift-ci
Copy link

openshift-ci bot commented Jan 22, 2022

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2043806, which is invalid:

  • expected dependent Bugzilla bug 2042493 to target a release in 4.11.0, but it targets "4.10.0" instead

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

In response to this:

[release-4.10] Bug 2043806: UPSTREAM 107564: kube-apiserver integration test: allow IPs with leading zeros on the API

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.

@openshift-ci openshift-ci bot requested review from deads2k and marun January 22, 2022 03:20
@aojea
Copy link

aojea commented Jan 26, 2022

/assign @soltysh @sttts

@sttts
Copy link

sttts commented Feb 1, 2022

/retest

@sttts
Copy link

sttts commented Feb 1, 2022

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 1, 2022
@openshift-ci
Copy link

openshift-ci bot commented Feb 1, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, sttts

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 Feb 1, 2022
@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

9 similar comments
@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

11 similar comments
@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@aojea
Copy link

aojea commented Feb 3, 2022

/test e2e-aws-csi

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@aojea
Copy link

aojea commented Feb 3, 2022

different error this time

ts_mgmt/v1/certificates returned HTTP 403: {"id":"11","kind":"Error","href":"/api/accounts_mgmt/v1/errors/11","code":"ACCT-MGMT-11","reason":"Account with ID 1CzKMWTzDbeN7jOMmO5Ar1Y3Ai1 denied access to perform create on Certificate with HTTP call POST /api/accounts_mgmt/v1/certificates","operation_id":"2befafb8-95e4-4321-aea2-0b504a6d24b3"}
level=info msg=Cluster operator monitoring Available is False with UpdatingPrometheusK8SFailed: Rollout of the monitoring stack failed and is degraded. Please investigate the degraded status error.
level=info msg=Cluster operator monitoring Pro

/test e2e-aws-csi

@openshift-bot
Copy link

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci
Copy link

openshift-ci bot commented Feb 4, 2022

@openshift-bot: This pull request references Bugzilla bug 2043806, which is invalid:

  • expected the bug to target the "4.10.0" release, but it targets "4.10.z" instead
  • expected dependent Bugzilla bug 2042493 to target a release in 4.11.0, but it targets "4.10.0" instead

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

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

@mfojtik mfojtik added the staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). label Feb 4, 2022
@aojea
Copy link

aojea commented Feb 4, 2022

/bugzilla refresh

@openshift-ci openshift-ci bot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Feb 4, 2022
@openshift-ci
Copy link

openshift-ci bot commented Feb 4, 2022

@aojea: This pull request references Bugzilla bug 2043806, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.10.0) matches configured target release for branch (4.10.0)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2042493 is in the state VERIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Bugzilla bug 2042493 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0
  • bug has dependents

Requesting review from QA contact:
/cc @wangke19

In response to this:

/bugzilla 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 kubernetes/test-infra repository.

@openshift-ci openshift-ci bot requested a review from wangke19 February 4, 2022 09:29
@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@gangwgr
Copy link

gangwgr commented Feb 4, 2022

/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 Feb 4, 2022
@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci
Copy link

openshift-ci bot commented Feb 4, 2022

@openshift-cherrypick-robot: 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-robot openshift-merge-robot merged commit 2fac222 into openshift:release-4.10 Feb 4, 2022
@openshift-ci
Copy link

openshift-ci bot commented Feb 4, 2022

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

Bugzilla bug 2043806 has been moved to the MODIFIED state.

In response to this:

[release-4.10] Bug 2043806: UPSTREAM 107564: kube-apiserver integration test: allow IPs with leading zeros on the API

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@deads2k deads2k Awaiting requested review from deads2k

@marun marun Awaiting requested review from marun

@wangke19 wangke19 Awaiting requested review from wangke19

Assignees

@soltysh soltysh

@sttts sttts

@aojea aojea

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/validated-commits Indicates that all commits come to merged upstream PRs. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged. staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead).
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
10 participants
@openshift-cherrypick-robot @openshift-ci-robot @aojea @sttts @openshift-bot @sosiouxme @gangwgr @mfojtik @soltysh @openshift-merge-robot