Bug 1594144

Summary:	Service atomic-openshift-node is still running if set the wrong value for parameter perFSGroup
Product:	OpenShift Container Platform	Reporter:	Chao Yang <chaoyang>
Component:	Node	Assignee:	Seth Jennings <sjenning>
Status:	CLOSED ERRATA	QA Contact:	Chao Yang <chaoyang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.10.0	CC:	aos-bugs, aos-storage-staff, jokerman, mmccomas
Target Milestone:	---
Target Release:	3.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-11 07:20:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Chao Yang 2018-06-22 09:01:24 UTC

Description of problem:
Service atomic-openshift-node is still running if set the wrong value for parameter perFSGroup

Version-Release number of selected component (if applicable):
openshift v3.10.3
kubernetes v1.10.0+b81c8f8

How reproducible:
Always

Steps to Reproduce:
1.oc edit configmap qe-compute 
2.set the value perFSGroup to -512Mi
3.restart atomic-openshift-node

Actual results:
Service atomic-openshift-node.service is still running

Expected results:
Service atomic-openshift-node.service should not ready

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:

Comment 3 Seth Jennings 2018-08-07 17:59:23 UTC

Origin PR:
https://github.com/openshift/origin/pull/20564

Comment 5 Chao Yang 2018-09-04 05:53:44 UTC

It is passed on 
openshift v3.11.0-0.25.0
kubernetes v1.11.0+d4cacc0

Sep 04 01:26:47 ip-172-18-1-18.ec2.internal atomic-openshift-node[27054]: F0904 01:26:47.428581   27054 server.go:245] Local quota setup failed: perFSGroup must be a positive quantity

Comment 7 errata-xmlrpc 2018-10-11 07:20:54 UTC

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:2652