[release-5.0] MG-234: REDUCE_LOGS=compress_logs compresses large must-gather logs before rsync

[openshift-cherrypick-robot]

This is an automated cherry-pick of #559

/assign shivprakashmuley

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: MG-234

Details

In response to this:

This is an automated cherry-pick of #559

/assign shivprakashmuley

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 openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 750a7a42-6619-4244-aac6-df6d59bb27cf

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[shivprakashmuley]

/lgtm

[openshift-merge-bot]

Scheduling required tests:
/test e2e-aws

[shivprakashmuley]

/verified by @shivprakashmuley
in #559

[openshift-ci-robot]

@shivprakashmuley: This PR has been marked as verified by @shivprakashmuley.

Details

In response to this:

/verified by @shivprakashmuley
in #559

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 openshift-eng/jira-lifecycle-plugin repository.

[shivprakashmuley]

/pipeline required

[openshift-merge-bot]

Scheduling required tests:
/test e2e-aws

[ardaguclu]

This is not the best practice. But I understand that you want to deliver this feature in 5.0 too. Considering that new feature is gated behind a feature gate, it is safe to backport it.
/lgtm
/approve
/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ardaguclu, openshift-cherrypick-robot, shivprakashmuley

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:

• OWNERS [ardaguclu]

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

[openshift-ci]

@ardaguclu: The label(s) backport-risk-assessed cannot be applied or removed, because you are not in one of the allowed teams and are not an allowed user. Must be a member of one of these teams: openshift-patch-managers, openshift-release-oversight, openshift-staff-engineers, openshift-sustaining-engineers

Details

In response to this:

This is not the best practice. But I understand that you want to deliver this feature in 5.0 too. Considering that new feature is gated behind a feature gate, it is safe to backport it.
/lgtm
/approve
/label backport-risk-assessed

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.

[praveencodes]

This is not the best practice. But I understand that you want to deliver this feature in 5.0 too. Considering that new feature is gated behind a feature gate, it is safe to backport it. /lgtm /approve /label backport-risk-assessed

So, I guess the normal PR against release-5.0 branch is sufficient for this without using cherrypick bot?

[openshift-ci]

@openshift-cherrypick-robot: all tests passed!

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-sigs/prow repository. I understand the commands that are listed here.