Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[openshift-logging] Use operand images from promoted 5.y tag #21422

Merged

Conversation

@jcantrill
Copy link
Contributor

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 31, 2021
@jcantrill
Copy link
Contributor

/lgtm

@periklis
Copy link
Contributor Author

periklis commented Sep 1, 2021

/test pj-rehearse
/test pj-rehearse-blocking

@periklis
Copy link
Contributor Author

periklis commented Sep 1, 2021

/retest

@periklis
Copy link
Contributor Author

periklis commented Sep 1, 2021

/retest

@periklis
Copy link
Contributor Author

periklis commented Sep 1, 2021

/test pj-rehearse

@periklis
Copy link
Contributor Author

periklis commented Sep 1, 2021

/test pj-rehearse

@periklis
Copy link
Contributor Author

periklis commented Sep 1, 2021

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 1, 2021

@periklis: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Rerun command
ci/prow/pj-rehearse-blocking b486a4f84a8f09ae22bdde06b47cee628594f352 link /test pj-rehearse-blocking
ci/rehearse/openshift/cluster-logging-operator/release-5.0/e2e-operator 2d4ea097258126b33306a06ee0f1364756993838 link /test pj-rehearse
ci/rehearse/openshift/elasticsearch-operator/release-5.0/cluster-logging-operator-e2e 2d4ea097258126b33306a06ee0f1364756993838 link /test pj-rehearse
ci/rehearse/openshift/elasticsearch-operator/release-5.0/e2e-operator 2d4ea097258126b33306a06ee0f1364756993838 link /test pj-rehearse

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.

Copy link
Contributor

@igor-karpukhin igor-karpukhin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 2, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 2, 2021

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

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 8ac5693 into openshift:master Sep 2, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 2, 2021

@periklis: Updated the following 2 configmaps:

  • ci-operator-misc-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-cluster-logging-operator-release-5.1.yaml using file ci-operator/config/openshift/cluster-logging-operator/openshift-cluster-logging-operator-release-5.1.yaml
    • key openshift-cluster-logging-operator-release-5.2.yaml using file ci-operator/config/openshift/cluster-logging-operator/openshift-cluster-logging-operator-release-5.2.yaml
    • key openshift-elasticsearch-operator-release-5.1.yaml using file ci-operator/config/openshift/elasticsearch-operator/openshift-elasticsearch-operator-release-5.1.yaml
    • key openshift-elasticsearch-operator-release-5.2.yaml using file ci-operator/config/openshift/elasticsearch-operator/openshift-elasticsearch-operator-release-5.2.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

In response to this:

This PR addresses switching cluster-logging-operator and elasticsearch-operator to consume operand images from logging/5.y imagestream tag. This is a follow up of:

To address: https://issues.redhat.com/browse/LOG-1637

/cc @jcantrill @vimalk78
/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
4 participants