Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1531439

Summary: EventRateLimiter can not be enabled and got error "no kind is registered for the type runtime.Unknown"
Product: OpenShift Container Platform Reporter: weiwei jiang <wjiang>
Component: MasterAssignee: Stefan Schimanski <sttts>
Status: CLOSED CURRENTRELEASE QA Contact: weiwei jiang <wjiang>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.9.0CC: aos-bugs, deads, dma, jokerman, mfojtik, mmccomas, smunilla, wjiang
Target Milestone: ---   
Target Release: 3.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openshift v3.9.0-0.21.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-13 14:53:42 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 weiwei jiang 2018-01-05 06:08:18 UTC
Description of problem:
After append EventRateLimiter configuration in master-config.yaml, got "no kind is registered for the type runtime.Unknown" when restart atomic-openshift-master-api.

but work well on 
# openshift version 
openshift v3.8.18
kubernetes v1.8.1+0d5291c
etcd 3.2.8


Version-Release number of selected component (if applicable):
# openshift version 
openshift v3.9.0-0.16.0
kubernetes v1.9.0-beta1
etcd 3.2.8


How reproducible:
Always

Steps to Reproduce:
1. Given master-config is merged with following lines:
admissionConfig:
  pluginOrderOverride:
  - EventRateLimit
  pluginConfig:
    EventRateLimit:
      configuration:
        apiVersion: eventratelimit.admission.k8s.io/v1alpha1 
        kind: Configuration
        limits:
        - type: Server
          qps: 1
          burst: 10
2. Restart atomic-openshift-master-api service
3. Check if atomic-openshift-master-api is started

Actual results:
# journalctl -f -u atomic-openshift-master-api 
-- Logs begin at Thu 2018-01-04 22:01:34 EST. --
Jan 05 00:57:59 ip-172-18-1-64.ec2.internal atomic-openshift-master-api[80554]: I0105 00:57:59.202851   80554 plugins.go:91] Registered admission plugin "SecurityContextDeny"
Jan 05 00:57:59 ip-172-18-1-64.ec2.internal atomic-openshift-master-api[80554]: I0105 00:57:59.202859   80554 plugins.go:91] Registered admission plugin "ServiceAccount"
Jan 05 00:57:59 ip-172-18-1-64.ec2.internal atomic-openshift-master-api[80554]: I0105 00:57:59.202865   80554 plugins.go:91] Registered admission plugin "DefaultStorageClass"
Jan 05 00:57:59 ip-172-18-1-64.ec2.internal atomic-openshift-master-api[80554]: I0105 00:57:59.202871   80554 plugins.go:91] Registered admission plugin "PersistentVolumeClaimResize"
Jan 05 00:57:59 ip-172-18-1-64.ec2.internal atomic-openshift-master-api[80554]: I0105 00:57:59.202877   80554 plugins.go:91] Registered admission plugin "PVCProtection"
Jan 05 00:57:59 ip-172-18-1-64.ec2.internal atomic-openshift-master-api[80554]: F0105 00:57:59.205046   80554 start_api.go:67] no kind is registered for the type runtime.Unknown
Jan 05 00:57:59 ip-172-18-1-64.ec2.internal systemd[1]: atomic-openshift-master-api.service: main process exited, code=exited, status=255/n/a
Jan 05 00:57:59 ip-172-18-1-64.ec2.internal systemd[1]: Failed to start Atomic OpenShift Master API.
Jan 05 00:57:59 ip-172-18-1-64.ec2.internal systemd[1]: Unit atomic-openshift-master-api.service entered failed state.
Jan 05 00:57:59 ip-172-18-1-64.ec2.internal systemd[1]: atomic-openshift-master-api.service failed.


Expected results:
Should not got error and work well

Additional info:

Comment 1 Michal Fojtik 2018-01-09 11:13:25 UTC
Seems like the   

pluginOrderOverride:
  - EventRateLimit

is causing this. Can you remove it?

David, seems like the error is wrong, I guess https://github.com/openshift/origin/pull/10013 should print a warning in case two admission chains are used?

Comment 4 weiwei jiang 2018-01-18 02:12:16 UTC
Will give a check once v3.9.0-0.21.0 come out.

Comment 5 weiwei jiang 2018-01-19 03:11:56 UTC
Checked with
# openshift version 
openshift v3.9.0-0.21.0
kubernetes v1.9.1+a0ce1bc657
etcd 3.2.8

And the issue can not be reproduced, so verify this.