[wip]OTA-1813: Extend alert risk e2e#1371
Conversation
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Excluded labels (none allowed) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hongkailiu The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@hongkailiu: This pull request references OTA-1813 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.22.0" version, but no target version was set. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
abe6812 to
1a42691
Compare
| g.By("Using fauxinnati as the upstream and its simple channel") | ||
| cv.Spec.Upstream = util.FauxinnatiAPIURL | ||
| cv.Spec.Channel = "simple" | ||
| cv.Spec.Channel = "OTA-1813" |
There was a problem hiding this comment.
The channel will return something like this:
$ curl "https://fauxinnati-fauxinnati.apps.ota-stage.q2z4.p1.openshiftapps.com/api/upgrades_info/graph?channel=OTA-1813&version=4.22.0-0.nightly-2026-04-06-051707&arch=amd64"
{
"nodes": [
{
"version": "4.22.0-0.nightly-2026-04-06-051707",
"payload": "quay.io/openshift-release-dev/ocp-release@sha256:00000000000000000000000000000000000000000000000000000000003d5ef0",
"metadata": {
"io.openshift.upgrades.graph.release.channels": "OTA-1813",
"io.openshift.upgrades.graph.release.manifestref": "sha256:00000000000000000000000000000000000000000000000000000000003d5ef0",
"url": "https://access.redhat.com/errata/RHSA-2024:06200"
}
},
{
"version": "4.22.1",
"payload": "quay.io/openshift-release-dev/ocp-release@sha256:00000000000000000000000000000000000000000000000000000000003d5ef1",
"metadata": {
"io.openshift.upgrades.graph.release.channels": "OTA-1813",
"io.openshift.upgrades.graph.release.manifestref": "sha256:00000000000000000000000000000000000000000000000000000000003d5ef1",
"url": "https://access.redhat.com/errata/RHSA-2024:06201"
}
},
{
"version": "4.22.2",
"payload": "quay.io/openshift-release-dev/ocp-release@sha256:00000000000000000000000000000000000000000000000000000000003d5ef2",
"metadata": {
"io.openshift.upgrades.graph.release.channels": "OTA-1813",
"io.openshift.upgrades.graph.release.manifestref": "sha256:00000000000000000000000000000000000000000000000000000000003d5ef2",
"url": "https://access.redhat.com/errata/RHSA-2024:06202"
}
}
],
"edges": [
[
0,
1
]
],
"conditionalEdges": [
{
"edges": [
{
"from": "4.22.0-0.nightly-2026-04-06-051707",
"to": "4.22.2"
}
],
"risks": [
{
"url": "https://docs.openshift.com/synthetic-risk-a",
"name": "SomeInvokerThing",
"message": "This is SomeInvokerThing that cannot be evaluated for testing purposes",
"matchingRules": [
{
"type": "PromQL",
"promql": {
"promql": "this will fail; muahaha"
}
}
]
}
]
}
]
}
|
/test e2e-agnostic-ovn-techpreview-serial-1of3 fauxinnati is redeployed a few mins ago. |
There was an issue of duplicated conditional risks when * a risk whose PromQL cannot be evaluated, and * the risk from alert was accepted. The issue is fixed by [cvo#1367](openshift#1367) and this pull is to extend the current alert risk e2e to cover the case.
1a42691 to
fb7df5b
Compare
|
@hongkailiu: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
|
Impressive. passed: (2m1s). |
|
Rerun for more confidence: /test e2e-agnostic-ovn-techpreview-serial-1of3 |
There was an issue of duplicated conditional risks when
a risk whose PromQL cannot be evaluated, and
the risk from alert was accepted.
The issue is fixed by cvo#1367 and this pull is to extend the current alert risk e2e to cover the case.