Skip to content

RFE-4149: Read only filesystem - temp directory mount#1014

Open
jacobsee wants to merge 2 commits into
openshift:mainfrom
jacobsee:read-only-fs-temp-dir
Open

RFE-4149: Read only filesystem - temp directory mount#1014
jacobsee wants to merge 2 commits into
openshift:mainfrom
jacobsee:read-only-fs-temp-dir

Conversation

@jacobsee

@jacobsee jacobsee commented Jul 10, 2025 •
edited
Loading

Copy link
Copy Markdown
Member

Add mounted temp dir so that the operator can write temp files, since the container fs is readonly.

This is due to an error encountered:

{"container":"console-operator","host":"ip-10-0-113-202.us-east-2.compute.internal","pod":"console-operator-56f7988cd4-25x75","_entry":"F0710 00:51:07.785045       1 cmd.go:182] mkdir /tmp/serving-cert-3208951600: read-only file system"}

@openshift-ci openshift-ci Bot requested review from TheRealJon and jhadvig July 10, 2025 17:59
@jacobsee jacobsee changed the title Read only filesystem - temp directory mount RFE-4149: Read only filesystem - temp directory mount Jul 10, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 10, 2025
@openshift-ci-robot

openshift-ci-robot commented Jul 10, 2025 •
edited by openshift-ci Bot
Loading

Copy link
Copy Markdown
Contributor

@jacobsee: This pull request references RFE-4149 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the feature request to target the "4.20.0" version, but no target version was set.

Details

In response to this:

Add mounted temp dir so that the operator can write temp files, since the container fs is readonly.

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-robot

openshift-ci-robot commented Jul 10, 2025 •
edited by openshift-ci Bot
Loading

Copy link
Copy Markdown
Contributor

@jacobsee: This pull request references RFE-4149 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the feature request to target the "4.20.0" version, but no target version was set.

Details

In response to this:

Add mounted temp dir so that the operator can write temp files, since the container fs is readonly.

This is due to an error encountered:

{"container":"console-operator","host":"ip-10-0-113-202.us-east-2.compute.internal","pod":"console-operator-56f7988cd4-25x75","_entry":"F0710 00:51:07.785045       1 cmd.go:182] mkdir /tmp/serving-cert-3208951600: read-only file system"}

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.

@jacobsee

jacobsee commented Jul 10, 2025

Copy link
Copy Markdown
Member Author

/retest

@dusk125

dusk125 commented Jul 22, 2025

Copy link
Copy Markdown

/lgtm
/retest-required

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

dusk125 commented Jul 22, 2025

Copy link
Copy Markdown

/assign @spadgett

@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 22, 2025
@dusk125

dusk125 commented Jul 22, 2025

Copy link
Copy Markdown

/lgtm

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

openshift-ci Bot commented Jul 22, 2025

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dusk125, jacobsee
Once this PR has been reviewed and has the lgtm label, please ask for approval from spadgett. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@dusk125

dusk125 commented Jul 23, 2025

Copy link
Copy Markdown

/retest-required

1 similar comment
@dusk125

dusk125 commented Jul 23, 2025

Copy link
Copy Markdown

/retest-required

@dusk125

dusk125 commented Jul 23, 2025

Copy link
Copy Markdown

/retest

@dusk125

dusk125 commented Jul 24, 2025

Copy link
Copy Markdown

/retest-required

2 similar comments
@dusk125

dusk125 commented Jul 24, 2025

Copy link
Copy Markdown

/retest-required

@jacobsee

jacobsee commented Jul 24, 2025

Copy link
Copy Markdown
Member Author

/retest-required

@openshift-ci

openshift-ci Bot commented Jul 25, 2025

Copy link
Copy Markdown
Contributor

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

@openshift-bot

openshift-bot commented Oct 23, 2025

Copy link
Copy Markdown
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d 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 23, 2025
@dusk125

dusk125 commented Oct 23, 2025

Copy link
Copy Markdown

/remove-lifecycle stale

@openshift-ci openshift-ci Bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 23, 2025
@openshift-bot

openshift-bot commented Jan 22, 2026

Copy link
Copy Markdown
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d 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 Jan 22, 2026
@dusk125

dusk125 commented Jan 22, 2026

Copy link
Copy Markdown

/remove-lifecycle stale

@openshift-ci openshift-ci Bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 22, 2026
@openshift-bot

openshift-bot commented Apr 23, 2026

Copy link
Copy Markdown
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d 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 Apr 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jhadvig jhadvig Awaiting requested review from jhadvig

@TheRealJon TheRealJon Awaiting requested review from TheRealJon

Assignees

@spadgett spadgett

@dusk125 dusk125

Labels

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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@jacobsee @openshift-ci-robot @dusk125 @openshift-bot @spadgett