openshift
MCO-2006: move node-filecycle monitor to default
We are migrating the MCO test cases from the private repo to the MCO repo.
When we have migrated the pinimagesets test cases, executed in a disruptive test suite, the node-lifecycle started failing reporting diskpressure, nodes not ready and unreachable. It was cased by our tests that enforce those scenarios in the nodes to make sure that the pinimagesets functionality is working fine.
In this PR we move the node-lifecycle monitor tests from Universal to Default, so that they are not executed in disruptive test suites.
Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.
For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.
This repository is configured in: automatic mode
@sergiordlr: This pull request references MCO-2006 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.21.0" version, but no target version was set.
In response to this:
We are migrating the MCO test cases from the private repo to the MCO repo.
When we have migrated the pinimagesets test cases, executed in a disruptive test suite, the node-lifecycle started failing reporting diskpressure, nodes not ready and unreachable. It was cased by our tests that enforce those scenarios in the nodes to make sure that the pinimagesets functionality is working fine.
In this PR we move the node-lifecycle monitor tests from Universal to Default, so that they are not executed in disruptive test suites.
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.
Scheduling required tests: /test e2e-aws-csi /test e2e-aws-ovn-fips /test e2e-aws-ovn-microshift /test e2e-aws-ovn-microshift-serial /test e2e-aws-ovn-serial-1of2 /test e2e-aws-ovn-serial-2of2 /test e2e-gcp-csi /test e2e-gcp-ovn /test e2e-gcp-ovn-upgrade /test e2e-metal-ipi-ovn-ipv6 /test e2e-vsphere-ovn /test e2e-vsphere-ovn-upi
@sergiordlr: This PR was included in a payload test run from openshift/machine-config-operator#5466 trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
- periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-aws-mco-fips-proxy-longduration
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/73bc4330-d5da-11f0-9bb4-9cb64c814439-0
![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: neisw, sergiordlr
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [neisw]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@sergiordlr: all tests passed!
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.
The payload job with both PRs reported all tests passing and no issue.
/verified by @sergiordlr
@sergiordlr: This PR has been marked as verified by @sergiordlr.
In response to this:
The payload job with both PRs reported all tests passing and no issue.
/verified by @sergiordlr
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.