Bug 1594144 - Service atomic-openshift-node is still running if set the wrong value for parameter perFSGroup
Summary: Service atomic-openshift-node is still running if set the wrong value for par...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.11.0
Assignee: Seth Jennings
QA Contact: Chao Yang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-22 09:01 UTC by Chao Yang
Modified: 2018-10-11 07:21 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-10-11 07:20:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 0 None None None 2018-10-11 07:21:18 UTC

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
Note You need to log in before you can comment on or make changes to this bug.