Skip to content

TRT-2776: Fix nginx PID file permission denied under restricted SCC#16

Closed
jhadvig wants to merge 1 commit into
openshift:mainfrom
jhadvig:fix-nginx-pid
Closed

TRT-2776: Fix nginx PID file permission denied under restricted SCC#16
jhadvig wants to merge 1 commit into
openshift:mainfrom
jhadvig:fix-nginx-pid

Conversation

@jhadvig

@jhadvig jhadvig commented Jul 14, 2026

Copy link
Copy Markdown
Member

Summary

Add /run to the chgrp/chmod block so nginx can write its PID file when running as non-root under OpenShift's restricted SCC.

Why

nginx writes to /run/nginx.pid at startup. The container runs as UID 1001 under the restricted SCC, so /run/ must be group-writable. PR #14 fixed the nginx binary issue but missed this directory, causing:

nginx: [emerg] open() "/run/nginx.pid" failed (13: Permission denied)

This results in the console plugin pod crash-looping on every TechPreview cluster, triggering CVO ClusterOperatorDegraded alerts and blocking CVO PR #1423 (the un-revert of #1398).

Test plan

  • CI image build passes
  • Container starts without PID file permission errors

🤖 Generated with Claude Code

nginx writes its PID to /run/nginx.pid at startup. Under OpenShift's
restricted SCC the container runs as non-root (UID 1001), so /run/
must be group-writable. Add /run to the existing chgrp/chmod block.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@openshift-ci-robot

openshift-ci-robot commented Jul 14, 2026

Copy link
Copy Markdown

@jhadvig: This pull request references TRT-2776 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 bug to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

Add /run to the chgrp/chmod block so nginx can write its PID file when running as non-root under OpenShift's restricted SCC.

Why

nginx writes to /run/nginx.pid at startup. The container runs as UID 1001 under the restricted SCC, so /run/ must be group-writable. PR #14 fixed the nginx binary issue but missed this directory, causing:

nginx: [emerg] open() "/run/nginx.pid" failed (13: Permission denied)

This results in the console plugin pod crash-looping on every TechPreview cluster, triggering CVO ClusterOperatorDegraded alerts and blocking CVO PR #1423 (the un-revert of #1398).

Test plan

  • CI image build passes
  • Container starts without PID file permission errors

🤖 Generated with Claude Code

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 added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 14, 2026
@openshift-ci
openshift-ci Bot requested review from hongkailiu and wking July 14, 2026 19:03
@openshift-ci

openshift-ci Bot commented Jul 14, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhadvig

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 14, 2026
@openshift-ci

openshift-ci Bot commented Jul 14, 2026

Copy link
Copy Markdown

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

@jhadvig

jhadvig commented Jul 14, 2026

Copy link
Copy Markdown
Member Author

Closing in favor of #17

@jhadvig jhadvig closed this Jul 14, 2026
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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants