Skip to content

[release-4.22] OCPBUGS-100305: Fix cache path to avoid /var/cache/dnf conflict - #783

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.22from
ericahinkleRH:OCPBUGS-89330-4.22
Jul 31, 2026
Merged

[release-4.22] OCPBUGS-100305: Fix cache path to avoid /var/cache/dnf conflict#783
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.22from
ericahinkleRH:OCPBUGS-89330-4.22

Conversation

@ericahinkleRH

@ericahinkleRH ericahinkleRH commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Backport of #779 to release-4.22

Jira: https://redhat.atlassian.net/browse/OCPBUGS-100305

This fixes CrashLoopBackOff on startup due to chmod /var/cache/dnf operation not permitted by using dedicated cache directories instead of conflicting with system paths.

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 30, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@ericahinkleRH: This pull request references Jira Issue OCPBUGS-89330, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the bug to target either version "4.22." or "openshift-4.22.", but it targets "5.0.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead
  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-89330 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Backport of #779 to release-4.22

Jira: https://redhat.atlassian.net/browse/OCPBUGS-89330

This fixes CrashLoopBackOff on startup due to chmod /var/cache/dnf operation not permitted by using dedicated cache directories instead of conflicting with system paths.

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

coderabbitai Bot commented Jul 30, 2026

Copy link
Copy Markdown

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: 265316c9-8093-4a03-8404-847ff7b1933e

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.

@openshift-ci
openshift-ci Bot requested review from dtfranz and trgeiger July 30, 2026 14:38
OCPBUGS-89330: Change catalogd and operator-controller cache directories
to use dedicated paths instead of conflicting with system paths like
/var/cache/dnf which cause permission errors on startup.

- catalogd: /var/cache/ -> /var/cache/catalogd
- operator-controller: /var/cache -> /var/cache/operator-controller
@ericahinkleRH ericahinkleRH changed the title [release-4.22] OCPBUGS-89330: Synchronize From Upstream Repositories OCPBUGS-89330 - Fix cache path to avoid /var/cache/dnf conflict Jul 30, 2026
@openshift-ci-robot openshift-ci-robot removed jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 30, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@ericahinkleRH: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

Backport of #779 to release-4.22

Jira: https://redhat.atlassian.net/browse/OCPBUGS-100305

This fixes CrashLoopBackOff on startup due to chmod /var/cache/dnf operation not permitted by using dedicated cache directories instead of conflicting with system paths.

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.

@ericahinkleRH ericahinkleRH changed the title OCPBUGS-89330 - Fix cache path to avoid /var/cache/dnf conflict OCPBUGS-100305 Fix cache path to avoid /var/cache/dnf conflict Jul 30, 2026
@ericahinkleRH

Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown

@ericahinkleRH: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

/jira refresh

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.

@ericahinkleRH ericahinkleRH changed the title OCPBUGS-100305 Fix cache path to avoid /var/cache/dnf conflict OCPBUGS-100305: Fix cache path to avoid /var/cache/dnf conflict Jul 30, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 30, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@ericahinkleRH: This pull request references Jira Issue OCPBUGS-100305, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-89330 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is Closed (Done) instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Backport of #779 to release-4.22

Jira: https://redhat.atlassian.net/browse/OCPBUGS-100305

This fixes CrashLoopBackOff on startup due to chmod /var/cache/dnf operation not permitted by using dedicated cache directories instead of conflicting with system paths.

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.

@ericahinkleRH

Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown

@ericahinkleRH: This pull request references Jira Issue OCPBUGS-100305, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

@ericahinkleRH

Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 30, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@ericahinkleRH: This pull request references Jira Issue OCPBUGS-100305, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-89330 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-89330 targets the "5.0.0" version, which is one of the valid target versions: 5.0.0
  • bug has dependents
Details

In response to this:

/jira refresh

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.

@ericahinkleRH ericahinkleRH changed the title OCPBUGS-100305: Fix cache path to avoid /var/cache/dnf conflict [release-4.22] OCPBUGS-100305: Fix cache path to avoid /var/cache/dnf conflict Jul 30, 2026
@tmshort

tmshort commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

/lgtm

@ericahinkleRH

Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-ovn-upgrade

@tmshort

tmshort commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 30, 2026
@openshift-ci

openshift-ci Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ericahinkleRH, tmshort

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 openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 30, 2026
@tmshort

tmshort commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

This can be verified via /verified by CI once the CI passes.

@openshift-ci

openshift-ci Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

@ericahinkleRH: 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.

@dtfranz

dtfranz commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jul 31, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@dtfranz: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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.

@joelanford

Copy link
Copy Markdown
Member

/label backport-risk-assessed

@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 Jul 31, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit f80de29 into openshift:release-4.22 Jul 31, 2026
13 checks passed
@openshift-ci-robot

Copy link
Copy Markdown

@ericahinkleRH: Jira Issue Verification Checks: Jira Issue OCPBUGS-100305
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-100305 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Backport of #779 to release-4.22

Jira: https://redhat.atlassian.net/browse/OCPBUGS-100305

This fixes CrashLoopBackOff on startup due to chmod /var/cache/dnf operation not permitted by using dedicated cache directories instead of conflicting with system paths.

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.

@ericahinkleRH

Copy link
Copy Markdown
Contributor Author

/cherry-pick release-4.21

@openshift-cherrypick-robot

Copy link
Copy Markdown

@ericahinkleRH: new pull request created: #785

Details

In response to this:

/cherry-pick release-4.21

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.

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/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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.

7 participants