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

[loki] add loki-operator package to CLO's e2e jobs #32068

Merged
merged 9 commits into from Apr 4, 2023

Conversation

btaani
Copy link
Member

@btaani btaani commented Sep 7, 2022

This PR adds the necessary configurations to enable running ci e2e tests on cluster-logging with lokistack

@btaani
Copy link
Member Author

btaani commented Sep 7, 2022

/assign @periklis

@btaani
Copy link
Member Author

btaani commented Sep 12, 2022

/restest-required

@btaani
Copy link
Member Author

btaani commented Sep 12, 2022

/retest-required

@btaani btaani force-pushed the loki-env branch 2 times, most recently from 056d0d3 to ab26c8c Compare September 12, 2022 13:15
@btaani btaani force-pushed the loki-env branch 2 times, most recently from 8697f82 to 5b7c800 Compare September 12, 2022 19:17
@periklis
Copy link
Contributor

/test pj-rehearse

@btaani btaani force-pushed the loki-env branch 2 times, most recently from c0871fc to fa8acb1 Compare September 21, 2022 20:50
@periklis
Copy link
Contributor

/test pj-rehearse

@btaani
Copy link
Member Author

btaani commented Sep 22, 2022

/retest pj-rehearse

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 22, 2022

@btaani: The /retest command does not accept any targets.
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 build05-dry
  • /test check-gh-automation
  • /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 jira-lifecycle-config
  • /test openshift-image-mirror-mappings
  • /test ordered-prow-config
  • /test owners
  • /test pj-rehearse-blocking
  • /test pr-reminder-config
  • /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 sync-rover-groups
  • /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 vsphere-dry

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

  • pull-ci-openshift-release-check-gh-automation
  • 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-ordered-prow-config
  • pull-ci-openshift-release-master-owners
  • pull-ci-openshift-release-master-pj-rehearse
  • pull-ci-openshift-release-master-prow-config-filenames
  • pull-ci-openshift-release-master-prow-config-semantics
  • pull-ci-openshift-release-openshift-image-mirror-mappings
  • pull-ci-openshift-release-yamllint

In response to this:

/retest pj-rehearse

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.

@btaani
Copy link
Member Author

btaani commented Sep 22, 2022

/test pj-rehearse

@periklis
Copy link
Contributor

periklis commented Sep 22, 2022

/hold Depends on DPTP-2969

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 22, 2022
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 27, 2022
@openshift-bot
Copy link
Contributor

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d 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

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 27, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 31, 2023

@btaani: 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 build05-dry
  • /test check-gh-automation
  • /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 clusterimageset-validate
  • /test config
  • /test core-valid
  • /test correctly-sharded-config
  • /test deprecate-templates
  • /test generated-config
  • /test generated-dashboards
  • /test hive-dry
  • /test jira-lifecycle-config
  • /test openshift-image-mirror-mappings
  • /test ordered-prow-config
  • /test owners
  • /test pr-reminder-config
  • /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 sync-rover-groups
  • /test yamllint

The following commands are available to trigger optional jobs:

  • /test arm01-dry
  • /test vsphere-dry

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

  • pull-ci-openshift-release-check-gh-automation
  • 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-ordered-prow-config
  • pull-ci-openshift-release-master-owners
  • pull-ci-openshift-release-master-prow-config-filenames
  • pull-ci-openshift-release-master-prow-config-semantics
  • pull-ci-openshift-release-master-release-controller-config
  • pull-ci-openshift-release-openshift-image-mirror-mappings
  • pull-ci-openshift-release-yamllint

In response to this:

/test pj-rehearse

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.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 3, 2023
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 3, 2023
@hongkailiu
Copy link
Member

/pj-rehearse pull-ci-openshift-cluster-logging-operator-master-e2e-target

@hongkailiu
Copy link
Member

/pj-rehearse pull-ci-openshift-cluster-logging-operator-master-e2e-target

@periklis
Copy link
Contributor

periklis commented Apr 4, 2023

/approve
/lgtm

@periklis
Copy link
Contributor

periklis commented Apr 4, 2023

/pj-rehearse ack

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Apr 4, 2023
@periklis
Copy link
Contributor

periklis commented Apr 4, 2023

/hold cancel

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Apr 4, 2023
@periklis
Copy link
Contributor

periklis commented Apr 4, 2023

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 4, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: btaani, 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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 4, 2023
@periklis
Copy link
Contributor

periklis commented Apr 4, 2023

/remove-lifecycle rotten

@openshift-ci openshift-ci bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Apr 4, 2023
@openshift-merge-robot openshift-merge-robot merged commit 5cbd440 into openshift:master Apr 4, 2023
17 of 19 checks passed
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 4, 2023

@btaani: Updated the following 2 configmaps:

  • 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
  • job-config-master-presubmits configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-cluster-logging-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-logging-operator/openshift-cluster-logging-operator-master-presubmits.yaml

In response to this:

This PR adds the necessary configurations to enable running ci e2e tests on cluster-logging with lokistack

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 4, 2023

@btaani: 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/cluster-logging-operator/master/e2e fa8acb19e86e221b6ecb0a9e46faf22b741ced29 link unknown /test pj-rehearse
ci/prow/pj-rehearse fa8acb19e86e221b6ecb0a9e46faf22b741ced29 link false /test pj-rehearse
ci/prow/multi-arch-gen-valid fa8acb19e86e221b6ecb0a9e46faf22b741ced29 link true /test multi-arch-gen-valid
ci/prow/pr-reminder-config fa8acb19e86e221b6ecb0a9e46faf22b741ced29 link true /test pr-reminder-config
ci/rehearse/openshift/cluster-logging-operator/master/functional-target 1959f34fae414fa3d5584270df2eeae4d2ccbde9 link unknown /pj-rehearse pull-ci-openshift-cluster-logging-operator-master-functional-target
ci/rehearse/openshift/cluster-logging-operator/master/ci-index-cluster-logging-operator-bundle 1959f34fae414fa3d5584270df2eeae4d2ccbde9 link unknown /pj-rehearse pull-ci-openshift-cluster-logging-operator-master-ci-index-cluster-logging-operator-bundle
ci/rehearse/openshift/cluster-logging-operator/master/e2e-target ca5611d link unknown /pj-rehearse pull-ci-openshift-cluster-logging-operator-master-e2e-target

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.

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. rehearsals-ack Signifies that rehearsal jobs have been acknowledged
Projects
None yet
7 participants