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
Bug 1916373: upi: allow IPsec ports #4552
Bug 1916373: upi: allow IPsec ports #4552
Conversation
@markdgray: This pull request references Bugzilla bug 1916373, which is invalid:
Comment 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. |
8c1e7b7
to
7048c10
Compare
7048c10
to
618d4ef
Compare
/retest |
/bugzilla refresh |
@markdgray: This pull request references Bugzilla bug 1916373, 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. 3 validation(s) were run on this bug
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is one discrepancy between the IPI and UPI. The rest looks good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/lgtm
Hold for passing UPI e2e tests.
/hold
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: staebler 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 |
/test e2e-aws-upi |
/retest |
The failures look to be unrelated flakes. /test e2e-aws-upi |
/test e2e-aws-upi |
timeouts during install "Get "https://registry.build02.ci.openshift.org/openshift/token?account=user&scope=repository%3Aci-op-r8d57l95%2Fstable%3Apull": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" /retest |
@staebler Do these look like known issues or could it be a bug in the rules? I am not familiar with these build jobs? |
The e2e-aws-upi test is failing on creating the resources, but from the history of that test it is not evident that it is related to the changes in this PR. I would still like to get at least a successful install, though. The e2e-gcp-upi test looks like it is broken missing a dependency. This is not related to the changes in this PR. It has been broken since at least July.
The e2e-openshift-upi test did have one green pass and is at least installing on other runs. I am satisfied with that. |
/test e2e-aws-upi |
4 similar comments
/test e2e-aws-upi |
/test e2e-aws-upi |
/test e2e-aws-upi |
/test e2e-aws-upi |
/hold cancel |
/retest Please review the full test history for this PR and help us cut down flakes. |
4 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@markdgray: The following tests failed, say
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. |
@markdgray: All pull requests linked via external trackers have merged: Bugzilla bug 1916373 has been moved to the MODIFIED state. 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. |
No description provided.