[wip] OTA-1580: Monitortest framework test for oc adm upgrade status
#29977
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@petr-muller: This pull request references OTA-1580 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 task to target the "4.20.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. |
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
petr-muller
changed the title
oc adm upgrade status"oc adm upgrade status
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: petr-muller The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/test e2e-gcp-ovn-upgrade |
|
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: ec4fdc7
New tests seen in this PR at sha: ec4fdc7
|
|
/test e2e-gcp-ovn-upgrade |
|
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: 4f64e9a
New tests seen in this PR at sha: 4f64e9a
|
|
/test e2e-gcp-ovn-upgrade |
3 similar comments
|
/test e2e-gcp-ovn-upgrade |
|
/test e2e-gcp-ovn-upgrade |
|
/test e2e-gcp-ovn-upgrade |
|
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: e4012f3
New tests seen in this PR at sha: e4012f3
|
openshift-merge-robot
added
the
needs-rebase
|
/test ? |
|
@JoelSpeed: The following commands are available to trigger required jobs: The following commands are available to trigger optional jobs: Use 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 kubernetes-sigs/prow repository. |
petr-muller
force-pushed
the
ota-1580-02-oc-adm-upgrade-status-on-update
branch
from
e4012f3 to
ae60c42
Compare
openshift-merge-robot
removed
the
needs-rebase
|
/test e2e-gcp-ovn-upgrade |
|
/test images lint unit verify verify-deps |
|
/test e2e-gcp-ovn |
|
Job Failure Risk Analysis for sha: 722553e
|
|
/test images lint unit verify verify-deps |
petr-muller
force-pushed
the
ota-1580-02-oc-adm-upgrade-status-on-update
branch
from
e6685f4 to
c13e0d4
Compare
|
/test images lint unit verify verify-deps |
|
/test e2e-aws-ovn-single-node-upgrade |
|
/test images lint unit verify verify-deps |
petr-muller
force-pushed
the
ota-1580-02-oc-adm-upgrade-status-on-update
branch
from
08099d3 to
0ca8da2
Compare
|
@petr-muller: This pull request references OTA-1580 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 task to target the "4.20.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. |
petr-muller
changed the title
oc adm upgrade statusoc adm upgrade status
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
petr-muller
changed the title
oc adm upgrade statusoc adm upgrade status
openshift-ci
bot
added
the
do-not-merge/work-in-progress
petr-muller
force-pushed
the
ota-1580-02-oc-adm-upgrade-status-on-update
branch
from
0ca8da2 to
9e1afe6
Compare
|
/retest-required |
|
Let's go hunting for $ curl -s https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/29977/pull-ci-openshift-origin-main-e2e-aws-disruptive/1948791765477625856/artifacts/e2e-aws-disruptive/openshift-e2e-test/build-log.txt | grep -c UpgradeStatus
0Shifting over to e2e-aws-ovn's Artifacts, the test step artifacts build log doesn't mention the test-case either: $ curl -s https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/29977/pull-ci-openshift-origin-main-e2e-aws-ovn/1948791765502791680/artifacts/e2e-aws-ovn/openshift-e2e-test/build-log.txt | grep -c UpgradeStatus
0but that step's JUnit artifacts have an $ curl -s https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/29977/pull-ci-openshift-origin-main-e2e-aws-ovn/1948791765502791680/artifacts/e2e-aws-ovn/openshift-e2e-test/artifacts/junit/e2e-monitor-tests__20250725-185304.xml | grep -1 OCPFeatureGate:UpgradeStatus
<testcase name="[Jira:"Node / Kubelet"] monitor test pod-lifecycle collection" time="0.001420344"></testcase>
<testcase name="[sig-cli][OCPFeatureGate:UpgradeStatus] oc amd upgrade status never fails" time="0"></testcase>
<testcase name="[Jira:"oc / update"] monitor test oc-adm-upgrade-status collection" time="0.001444186"></testcase>and over in $ curl -s https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/29977/pull-ci-openshift-origin-main-e2e-gcp-fips-serial-2of2/1948791811484946432/artifacts/e2e-gcp-fips-serial/openshift-e2e-test/artifacts/junit/e2e-monitor-tests__20250725-182108.xml | grep OCPFeatureGate:UpgradeStatus
<testcase name="[sig-cli][OCPFeatureGate:UpgradeStatus] oc amd upgrade status never fails" time="0"></testcase> |
|
@petr-muller: 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. |
|
/close in favor of #30031 |
openshift-merge-robot
added
the
needs-rebase
|
PR needs rebase. 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. |
|
@hongkailiu: Closed this PR. 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 kubernetes-sigs/prow repository. |
6 participants
TBD, SSIA