Open slashpai opened 5 months ago
@slashpai: This pull request references MON-3846 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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: slashpai
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@slashpai: This pull request references MON-3846 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.
/retest-required
/hold let's revisit this later after temporary fix #2334
@machine424 what do you think about proceeding with this or do we want to wait?
@slashpai: The following test 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-hypershift-conformance | a62691701ec876970a213d168347abe099c6b14f | link | true | /test e2e-hypershift-conformance |
Full PR test history. Your PR dashboard.
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
PR needs rebase.
This is to avoid similar situation like https://issues.redhat.com/browse/OCPBUGS-32510 so that metrics-server doesn't need to wait for prometheus task to create the configmap
cc: @machine424 @simonpasquier @jan--f