openshift
AGENT-715: Add tests for baremetal hosts for agent installer
Add a new directory for agent-installer related tests with first set of tests to check baremetal hosts. The baremetal hosts tests will also check that the BMC configuration is set properly when the provisioning network is enabled.
In order to exercise this test in CI it depends on the conformance tests being added by: https://github.com/openshift/release/pull/43917 In addition, an agent test must add this env variable in order to enable the provisioning network. AGENT_BM_HOSTS_IN_INSTALL_CONFIG=true
@bfournie: This pull request references AGENT-715 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.16.0" version, but no target version was set.
In response to this:
Add a new directory for agent-installer related tests with first set of tests to check baremetal hosts. The baremetal hosts tests will also check that the BMC configuration is set properly when the provisioning network is enabled.
In order to exercise this test in CI it depends on the conformance tests being added by: https://github.com/openshift/release/pull/43917 In addition, an agent test must add this env variable in order to enable the provisioning network. AGENT_BM_HOSTS_IN_INSTALL_CONFIG=true
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/test-infra repository.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: bfournie Once this PR has been reviewed and has the lgtm label, please assign soltysh for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@bfournie: The following tests 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-aws-ovn-upgrade | 629b00adc1a1901104d69c17dd76cb995f69c724 | link | false | /test e2e-aws-ovn-upgrade |
| ci/prow/e2e-aws-ovn-single-node-upgrade | 629b00adc1a1901104d69c17dd76cb995f69c724 | link | false | /test e2e-aws-ovn-single-node-upgrade |
| ci/prow/e2e-aws-ovn-single-node-serial | 629b00adc1a1901104d69c17dd76cb995f69c724 | link | false | /test e2e-aws-ovn-single-node-serial |
| ci/prow/e2e-metal-ipi-ovn-ipv6 | 629b00adc1a1901104d69c17dd76cb995f69c724 | link | true | /test e2e-metal-ipi-ovn-ipv6 |
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/test-infra repository. I understand the commands that are listed here.
Job Failure Risk Analysis for sha: 629b00adc1a1901104d69c17dd76cb995f69c724
| Job Name | Failure Risk |
|---|---|
| pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade | IncompleteTests Tests for this run (424) are below the historical average (2017): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems) |
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
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closed this PR.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen. Mark the issue as fresh by commenting/remove-lifecycle rotten. Exclude this issue from closing again by commenting/lifecycle frozen./close
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.