origin
origin copied to clipboard
openshift
HOSTEDCP-1466: auditloganalyzer: don't parse the URL unless we need to
@stevekuznetsov: This pull request references HOSTEDCP-1466 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.
In response to this:
/assign @deads2k
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.
INFO[2024-03-11T13:29:22Z] Tagging openshift/release:rhel-8-release-golang-1.20-openshift-4.16 into pipeline:root.
ERRO[2024-03-11T14:04:23Z] Could not resolve tag root in imagestream pipeline. error=timed out waiting for the condition
Seems like CI is busted for this repo ... ?
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: deads2k, stevekuznetsov
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [deads2k]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: deads2k, stevekuznetsov
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [deads2k]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/retest-required
Remaining retests: 0 against base HEAD 7379790951b7733515623911f647cdbdd3a1357a and 2 for PR HEAD 8067faca8d238ab26bd15847405f4c5602b69008 in total
/retest-required
Remaining retests: 0 against base HEAD 5d9cbd2982cc713753025e1afab6c7220ad2c5e7 and 1 for PR HEAD 8067faca8d238ab26bd15847405f4c5602b69008 in total
/retest-required
Remaining retests: 0 against base HEAD f1a21f4ac288b1e3ab13b0540fb216c37ab548e6 and 0 for PR HEAD 8067faca8d238ab26bd15847405f4c5602b69008 in total
@stevekuznetsov: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e-aws-ovn-fips | 8067faca8d238ab26bd15847405f4c5602b69008 | link | true | /test e2e-aws-ovn-fips |
| ci/prow/e2e-aws-ovn-single-node-upgrade | 8067faca8d238ab26bd15847405f4c5602b69008 | link | false | /test e2e-aws-ovn-single-node-upgrade |
| ci/prow/e2e-aws-ovn-single-node-serial | 8067faca8d238ab26bd15847405f4c5602b69008 | link | false | /test e2e-aws-ovn-single-node-serial |
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.
/hold
Revision 8067faca8d238ab26bd15847405f4c5602b69008 was retested 3 times: holding
Job Failure Risk Analysis for sha: 8067faca8d238ab26bd15847405f4c5602b69008
| Job Name | Failure Risk |
|---|---|
| pull-ci-openshift-origin-master-e2e-aws-ovn-fips | IncompleteTests Tests for this run (99) are below the historical average (1355): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems) |
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
@stevekuznetsov: Closed this PR.
In response to this:
/close
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.