Skip to content

Conversation

@andfasano
Copy link
Contributor

@andfasano andfasano commented Feb 2, 2022

This patch adds two new steps registry baremetal configurations (baremetalds-e2e-proxy-ipv4 and baremetalds-e2e-proxy-ipv6) for testing the installation by using a local proxy, and uses them for adding two new tests in the openshift-metal3/dev-scripts repo.

Requires openshift-metal3/dev-scripts#1341

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 2, 2022
@openshift-ci openshift-ci bot requested review from celebdor and russellb February 2, 2022 11:26
@andfasano
Copy link
Contributor Author

Will be used to test openshift/installer#5598

@andfasano andfasano force-pushed the baremetal-proxy-job branch from 60ca15f to 28418a2 Compare February 4, 2022 09:03
@andfasano
Copy link
Contributor Author

/test 4.9-e2e-metal-ipi

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 4, 2022

@andfasano: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test app-ci-config-dry
  • /test boskos-config
  • /test boskos-config-generation
  • /test build-clusters
  • /test build01-dry
  • /test build02-dry
  • /test build03-dry
  • /test build04-dry
  • /test ci-operator-config
  • /test ci-operator-config-metadata
  • /test ci-operator-registry
  • /test ci-secret-bootstrap-config-validation
  • /test ci-testgrid-allow-list
  • /test config
  • /test core-valid
  • /test correctly-sharded-config
  • /test deprecate-templates
  • /test generated-config
  • /test generated-dashboards
  • /test hive-dry
  • /test openshift-image-mirror-mappings
  • /test ordered-prow-config
  • /test owners
  • /test pj-rehearse-blocking
  • /test prow-config
  • /test prow-config-filenames
  • /test prow-config-semantics
  • /test pylint
  • /test release-config
  • /test release-controller-config
  • /test secret-generator-config-valid
  • /test services-valid
  • /test step-registry-metadata
  • /test step-registry-shellcheck
  • /test yamllint

The following commands are available to trigger optional jobs:

  • /test arm01-dry
  • /test pj-rehearse
  • /test pj-rehearse-max
  • /test pj-rehearse-more
  • /test sync-rover-groups
  • /test vsphere-dry

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-release-master-build-clusters
  • pull-ci-openshift-release-master-ci-operator-config
  • pull-ci-openshift-release-master-ci-operator-config-metadata
  • pull-ci-openshift-release-master-ci-operator-registry
  • pull-ci-openshift-release-master-config
  • pull-ci-openshift-release-master-core-valid
  • pull-ci-openshift-release-master-correctly-sharded-config
  • pull-ci-openshift-release-master-deprecate-templates
  • pull-ci-openshift-release-master-generated-config
  • pull-ci-openshift-release-master-generated-dashboards
  • pull-ci-openshift-release-master-ordered-prow-config
  • pull-ci-openshift-release-master-owners
  • pull-ci-openshift-release-master-pj-rehearse
  • pull-ci-openshift-release-master-prow-config
  • pull-ci-openshift-release-master-prow-config-filenames
  • pull-ci-openshift-release-master-prow-config-semantics
  • pull-ci-openshift-release-master-release-config
  • pull-ci-openshift-release-master-release-controller-config
  • pull-ci-openshift-release-master-secret-generator-config-valid
  • pull-ci-openshift-release-master-services-valid
  • pull-ci-openshift-release-master-step-registry-metadata
  • pull-ci-openshift-release-master-step-registry-shellcheck
  • pull-ci-openshift-release-openshift-image-mirror-mappings
  • pull-ci-openshift-release-yamllint
Details

In response to this:

/test 4.9-e2e-metal-ipi

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.

@andfasano
Copy link
Contributor Author

/test pj-rehearse

2 similar comments
@andfasano
Copy link
Contributor Author

/test pj-rehearse

@andfasano
Copy link
Contributor Author

/test pj-rehearse

@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 22, 2022
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 23, 2022
@andfasano
Copy link
Contributor Author

/test pj-rehearse

2 similar comments
@andfasano
Copy link
Contributor Author

/test pj-rehearse

@andfasano
Copy link
Contributor Author

/test pj-rehearse

@andfasano andfasano force-pushed the baremetal-proxy-job branch 2 times, most recently from ba38588 to 4be3cd2 Compare March 1, 2022 11:55
@andfasano
Copy link
Contributor Author

/test pj-rehearse

3 similar comments
@andfasano
Copy link
Contributor Author

/test pj-rehearse

@andfasano
Copy link
Contributor Author

/test pj-rehearse

@andfasano
Copy link
Contributor Author

/test pj-rehearse

@andfasano
Copy link
Contributor Author

/test pj-rehearse

1 similar comment
@andfasano
Copy link
Contributor Author

/test pj-rehearse

@andfasano andfasano force-pushed the baremetal-proxy-job branch from 4be3cd2 to 873fdaa Compare March 10, 2022 11:45
@andfasano
Copy link
Contributor Author

/test pj-rehearse

@andfasano andfasano force-pushed the baremetal-proxy-job branch from 873fdaa to 5b418c5 Compare March 14, 2022 17:14
@andfasano
Copy link
Contributor Author

/retest-required

@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 21, 2022
@andfasano andfasano force-pushed the baremetal-proxy-job branch from 5b418c5 to fabc79b Compare March 21, 2022 09:15
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 21, 2022
@andfasano
Copy link
Contributor Author

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 8, 2022

@andfasano: 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/rehearse/openshift-metal3/dev-scripts/master/e2e-metal-ipi-serial-ipv4 873fdaacaad0fcc2b99db644d081344b8dbd86d8 link unknown /test pj-rehearse
ci/prow/sync-rover-groups fabc79bc3a42553df32c7d3e4fe568f2d292641f link true /test sync-rover-groups

Full PR test history. Your PR dashboard.

Details

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.

@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 8, 2022
@andfasano andfasano force-pushed the baremetal-proxy-job branch from fabc79b to 2d360ca Compare April 22, 2022 07:43
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 22, 2022
@elfosardo
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 22, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 22, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andfasano, elfosardo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit 31b5021 into openshift:master Apr 22, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 22, 2022

@andfasano: Updated the following 3 configmaps:

  • ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-metal3-dev-scripts-master.yaml using file ci-operator/config/openshift-metal3/dev-scripts/openshift-metal3-dev-scripts-master.yaml
  • job-config-master-presubmits configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-metal3-dev-scripts-master-presubmits.yaml using file ci-operator/jobs/openshift-metal3/dev-scripts/openshift-metal3-dev-scripts-master-presubmits.yaml
  • step-registry configmap in namespace ci at cluster app.ci using the following files:
    • key OWNERS using file ci-operator/step-registry/baremetalds/e2e/proxy/OWNERS
    • key OWNERS using file ci-operator/step-registry/baremetalds/e2e/proxy/ipv4/OWNERS
    • key baremetalds-e2e-proxy-ipv4-workflow.metadata.json using file ci-operator/step-registry/baremetalds/e2e/proxy/ipv4/baremetalds-e2e-proxy-ipv4-workflow.metadata.json
    • key baremetalds-e2e-proxy-ipv4-workflow.yaml using file ci-operator/step-registry/baremetalds/e2e/proxy/ipv4/baremetalds-e2e-proxy-ipv4-workflow.yaml
    • key OWNERS using file ci-operator/step-registry/baremetalds/e2e/proxy/ipv6/OWNERS
    • key baremetalds-e2e-proxy-ipv6-workflow.metadata.json using file ci-operator/step-registry/baremetalds/e2e/proxy/ipv6/baremetalds-e2e-proxy-ipv6-workflow.metadata.json
    • key baremetalds-e2e-proxy-ipv6-workflow.yaml using file ci-operator/step-registry/baremetalds/e2e/proxy/ipv6/baremetalds-e2e-proxy-ipv6-workflow.yaml
Details

In response to this:

This patch adds two new steps registry baremetal configurations (baremetalds-e2e-proxy-ipv4 and baremetalds-e2e-proxy-ipv6) for testing the installation by using a local proxy, and uses them for adding two new tests in the openshift-metal3/dev-scripts repo.

Requires openshift-metal3/dev-scripts#1341

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants