Skip to content

Conversation

@periklis
Copy link
Contributor

@periklis periklis commented Dec 16, 2020

This PR is a follow-up of #14353 to fix using the COMPUTE_NODE_TYPE=m5.4xlarge for master, release-4.6 and release-4.5 CI jobs. It will enable addressing backports that currently hit also resource limits by using too small clusters.

/cc @jcantrill
/assign @jcantrill

@openshift-merge-robot
Copy link
Contributor

@periklis: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/rehearse/openshift/origin-aggregated-logging/release-4.5/cluster-logging-operator-e2e 40d5fb0613b454f46a88d145a9ef9de9bb701982 link /test pj-rehearse
ci/rehearse/openshift/origin-aggregated-logging/release-4.6/smoke 40d5fb0613b454f46a88d145a9ef9de9bb701982 link /test pj-rehearse
ci/rehearse/openshift/origin-aggregated-logging/release-4.5/smoke 40d5fb0613b454f46a88d145a9ef9de9bb701982 link /test pj-rehearse
ci/rehearse/openshift/cluster-logging-operator/release-4.5/e2e-operator 40d5fb0613b454f46a88d145a9ef9de9bb701982 link /test pj-rehearse
ci/rehearse/openshift/elasticsearch-proxy/release-4.5/cluster-logging-operator-e2e 40d5fb0613b454f46a88d145a9ef9de9bb701982 link /test pj-rehearse
ci/rehearse/openshift/elasticsearch-operator/release-4.5/cluster-logging-operator-e2e 40d5fb0613b454f46a88d145a9ef9de9bb701982 link /test pj-rehearse
ci/rehearse/openshift/cluster-logging-operator/release-4.6/e2e-operator 40d5fb0613b454f46a88d145a9ef9de9bb701982 link /test pj-rehearse
ci/prow/pj-rehearse 40d5fb0613b454f46a88d145a9ef9de9bb701982 link /test pj-rehearse

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.

@periklis periklis force-pushed the cl-cluster-node-types branch from 40d5fb0 to 6d0736b Compare December 16, 2020 13:32
@periklis periklis changed the title [openshift-logging] Declare cluster node types for 4.6 and 4.5 jobs [openshift-logging] Declare cluster node types for jobs Dec 16, 2020
@periklis periklis changed the title [openshift-logging] Declare cluster node types for jobs [openshift-logging] Declare compute node type for jobs Dec 16, 2020
@jcantrill
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 16, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcantrill, periklis

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-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 16, 2020
@openshift-merge-robot openshift-merge-robot merged commit f6b07b7 into openshift:master Dec 16, 2020
@openshift-ci-robot
Copy link
Contributor

@periklis: Updated the following 3 configmaps:

  • ci-operator-4.6-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-cluster-logging-operator-release-4.6.yaml using file ci-operator/config/openshift/cluster-logging-operator/openshift-cluster-logging-operator-release-4.6.yaml
    • key openshift-elasticsearch-operator-release-4.6.yaml using file ci-operator/config/openshift/elasticsearch-operator/openshift-elasticsearch-operator-release-4.6.yaml
    • key openshift-elasticsearch-proxy-release-4.6.yaml using file ci-operator/config/openshift/elasticsearch-proxy/openshift-elasticsearch-proxy-release-4.6.yaml
    • key openshift-origin-aggregated-logging-release-4.6.yaml using file ci-operator/config/openshift/origin-aggregated-logging/openshift-origin-aggregated-logging-release-4.6.yaml
  • ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-cluster-logging-operator-master.yaml using file ci-operator/config/openshift/cluster-logging-operator/openshift-cluster-logging-operator-master.yaml
    • key openshift-elasticsearch-operator-master.yaml using file ci-operator/config/openshift/elasticsearch-operator/openshift-elasticsearch-operator-master.yaml
    • key openshift-elasticsearch-proxy-master.yaml using file ci-operator/config/openshift/elasticsearch-proxy/openshift-elasticsearch-proxy-master.yaml
    • key openshift-origin-aggregated-logging-master.yaml using file ci-operator/config/openshift/origin-aggregated-logging/openshift-origin-aggregated-logging-master.yaml
  • ci-operator-4.5-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-cluster-logging-operator-release-4.5.yaml using file ci-operator/config/openshift/cluster-logging-operator/openshift-cluster-logging-operator-release-4.5.yaml
    • key openshift-elasticsearch-operator-release-4.5.yaml using file ci-operator/config/openshift/elasticsearch-operator/openshift-elasticsearch-operator-release-4.5.yaml
    • key openshift-elasticsearch-proxy-release-4.5.yaml using file ci-operator/config/openshift/elasticsearch-proxy/openshift-elasticsearch-proxy-release-4.5.yaml
    • key openshift-origin-aggregated-logging-release-4.5.yaml using file ci-operator/config/openshift/origin-aggregated-logging/openshift-origin-aggregated-logging-release-4.5.yaml
Details

In response to this:

This PR is a follow-up of #14353 to fix using the COMPUTE_NODE_TYPE=m5.4xlarge for master, release-4.6 and release-4.5 CI jobs. It will enable addressing backports that currently hit also resource limits by using too small clusters.

/cc @jcantrill
/assign @jcantrill

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.

4 participants