MCO-1520: Add MachineConfigNode e2e tests #29596
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@isabella-janssen: This pull request references MCO-1520 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.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
isabella-janssen
changed the title
|
@isabella-janssen: This pull request references MCO-1595 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.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@isabella-janssen: This pull request references MCO-1595 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.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@isabella-janssen: This pull request references MCO-1595 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.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
isabella-janssen
force-pushed
the
add-mcn-tests
branch
from
34cc5f0 to
dfa6f73
Compare
|
@isabella-janssen: This pull request references MCO-1595 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.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@isabella-janssen: This pull request references MCO-1595 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.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@isabella-janssen: This pull request references MCO-1595 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.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@isabella-janssen: This pull request references MCO-1595 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.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
isabella-janssen
changed the title
|
@isabella-janssen: This pull request references MCO-1520 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.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
isabella-janssen
force-pushed
the
add-mcn-tests
branch
2 times, most recently
from
379af77 to
cca6a6c
Compare
|
@isabella-janssen: This pull request references MCO-1520 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.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@isabella-janssen: This pull request references MCO-1520 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.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
isabella-janssen
force-pushed
the
add-mcn-tests
branch
3 times, most recently
from
32a7289 to
e23bc51
Compare
|
@isabella-janssen: This pull request references MCO-1520 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.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
isabella-janssen
force-pushed
the
add-mcn-tests
branch
from
7d7fe11 to
d8ddd80
Compare
|
@isabella-janssen: This pull request references MCO-1520 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.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
isabella-janssen
force-pushed
the
add-mcn-tests
branch
from
8afdf65 to
b3740b7
Compare
|
@isabella-janssen: This pull request references MCO-1520 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.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/retest-required |
2 similar comments
|
/retest-required |
|
/retest-required |
|
Job Failure Risk Analysis for sha: 3e8927a
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: 3e8927a
New tests seen in this PR at sha: 3e8927a
|
|
/retest-required |
|
Job Failure Risk Analysis for sha: 3e8927a
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: 3e8927a
New tests seen in this PR at sha: 3e8927a
|
|
Job Failure Risk Analysis for sha: 3e8927a
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: 3e8927a
New tests seen in this PR at sha: 3e8927a
|
|
/retest-required |
|
Job Failure Risk Analysis for sha: 3e8927a
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: 3e8927a
New tests seen in this PR at sha: 3e8927a
|
|
/retest-required |
|
/override ci/prow/e2e-aws-ovn-microshift |
|
@dgoodwin: Overrode contexts on behalf of dgoodwin: ci/prow/e2e-aws-ovn-microshift 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-sigs/prow repository. |
|
/retest-required |
|
/test e2e-vsphere-ovn-upi |
|
Job Failure Risk Analysis for sha: 3e8927a
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: 3e8927a
New tests seen in this PR at sha: 3e8927a
|
|
/retest-required |
|
Job Failure Risk Analysis for sha: 3e8927a
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: 3e8927a
New tests seen in this PR at sha: 3e8927a
|
|
Job Failure Risk Analysis for sha: 3e8927a
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: 3e8927a
New tests seen in this PR at sha: 3e8927a
|
|
@isabella-janssen: 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-sigs/prow repository. I understand the commands that are listed here. |
|
Job Failure Risk Analysis for sha: 3e8927a
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: 3e8927a
New tests seen in this PR at sha: 3e8927a
|
|
/retest-required |
openshift-merge-bot
bot
merged commit 019c9bd
into
openshift:main
|
[ART PR BUILD NOTIFIER] Distgit: openshift-enterprise-tests |
|
[ART PR BUILD NOTIFIER] Distgit: openshift-enterprise-tests |
|
[ART PR BUILD NOTIFIER] Distgit: openshift-enterprise-tests |
|
[ART PR BUILD NOTIFIER] Distgit: openshift-enterprise-tests |
Contributors: @isabella-janssen @pablintino @djoshy
Work Included
Notes
4.19.0-0.nightly-2025-03-21-030708or later with tech preview enabled.Slow, as they often take longer than 5 minutes to run. To have these tests run automatically, we will need to create a suite at a later time (Slack ref), but the tests can still be run locally.MCO-1595: Validate MCN properties
MCO-1596: Validate MCN condition status transitions
MCO-1597: Validate MCN condition status on node degrade
MCO-1598: Validate MCN on node creation and deletion
Note that this test is skipped for Single Node Openshift.
MCO-1599: Validate MCN object can only be accessible from its associated MCD
Note that these tests are skipped for Single Node Openshift.