Skip to content

[release-4.20] NO-ISSUE: Add root user option to write /loki/chunks inside the container#5759

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.20from
agullon:patch-25
Nov 18, 2025
Merged

[release-4.20] NO-ISSUE: Add root user option to write /loki/chunks inside the container#5759
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.20from
agullon:patch-25

Conversation

@agullon
Copy link
Contributor

@agullon agullon commented Nov 18, 2025

Add root user option to create/write /loki/chunks anywhere in the container

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 18, 2025
@openshift-ci-robot
Copy link

@agullon: This pull request explicitly references no jira issue.

Details

In response to this:

Add root user option to create/write /loki/chunks anywhere in the container

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.

@agullon
Copy link
Contributor Author

agullon commented Nov 18, 2025

/test e2e-aws-tests-bootc-release e2e-aws-tests-release e2e-aws-tests-bootc-release e2e-aws-tests-bootc-release-arm e2e-aws-tests-release-arm

@openshift-ci openshift-ci bot requested review from copejon and jerpeter1 November 18, 2025 11:40
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 18, 2025
@ggiguash
Copy link
Contributor

/label backport-risk-assessed
/lgtm
/verified by ci
/label jira/valid-bug

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Nov 18, 2025
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 18, 2025
@openshift-ci-robot
Copy link

@ggiguash: This PR has been marked as verified by ci.

Details

In response to this:

/label backport-risk-assessed
/lgtm
/verified by ci
/label jira/valid-bug

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.

@openshift-ci openshift-ci bot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Nov 18, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 18, 2025
@agullon
Copy link
Contributor Author

agullon commented Nov 18, 2025

@ggiguash I'd override failing tests because yesterday I fixed them in 6c0cdb9 from #5703 PR

@ggiguash
Copy link
Contributor

Overriding the failed release tests to make progress (they are not related to the current fix).
/override ci/prow/e2e-aws-tests-release
/override ci/prow/e2e-aws-tests-release-arm

/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 18, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, ggiguash

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
Copy link
Contributor

openshift-ci bot commented Nov 18, 2025

@ggiguash: Overrode contexts on behalf of ggiguash: ci/prow/e2e-aws-tests-release, ci/prow/e2e-aws-tests-release-arm

Details

In response to this:

Overriding the failed release tests to make progress (they are not related to the current fix).
/override ci/prow/e2e-aws-tests-release
/override ci/prow/e2e-aws-tests-release-arm

/lgtm

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 18, 2025

@agullon: 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/prow/e2e-aws-tests-release-arm cbbfa39 link true /test e2e-aws-tests-release-arm
ci/prow/e2e-aws-tests-release cbbfa39 link true /test e2e-aws-tests-release

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 0ccad8c into openshift:release-4.20 Nov 18, 2025
17 checks passed
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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants