Bug 1582610 – Subpath volume mount does not receive setgid by fsGroup

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1582610 - Subpath volume mount does not receive setgid by fsGroup

Summary:	Subpath volume mount does not receive setgid by fsGroup

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Storage (Show other bugs)
Sub Component:
Version:	3.7.0
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	---
Target Release:	3.7.z
Assigned To:	Bradley Childs
QA Contact:	Jianwei Hou
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1556757
Blocks:
	Show dependency tree / graph

Reported:	2018-05-25 14:39 EDT by hchen
Modified:	2018-06-07 04:41 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:	1556757
Environment:
Last Closed:	2018-06-07 04:40:57 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:1566	None	None	None	2018-05-25 14:39 EDT
Red Hat Product Errata	RHBA-2018:1798	None	None	None	2018-06-07 04:41 EDT

Groups: None (edit)

Comment 3 Jianwei Hou 2018-05-29 23:33:58 EDT

Verfied in v3.7.51

# oc exec subpath -- ls /mnt -l 
total 0
drwxrwsrwx    2 root     users            6 May 30 03:32 direct
drwxrwsrwx    2 root     users            6 May 30 03:32 subpath

Comment 5 errata-xmlrpc 2018-06-07 04:40:57 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:1798

Note You need to log in before you can comment on or make changes to this bug.