Red Hat Bugzilla – Bug 1452206
Constant short buffer/very short watch error messages for ClusterRoleBinding, ClusterRole and Role
Last modified: 2017-11-28 16:55:46 EST
Created attachment 1280046 [details] Master log Description of problem: May 18 10:23:21 ip-172-31-41-8 atomic-openshift-master: W0518 10:23:21.972019 9701 reflector.go:323] github.com/openshift/origin/pkg/authorization/generated/informers/internalversion/factory.go:45: watch of *api.ClusterRoleBinding ended with: very short watch May 18 10:23:21 ip-172-31-41-8 atomic-openshift-master: E0518 10:23:21.993961 9701 streamwatcher.go:109] Unable to decode an event from the watch stream: got short buffer with n=0, base=488, cap=2560 May 18 10:23:21 ip-172-31-41-8 atomic-openshift-master: W0518 10:23:21.993986 9701 reflector.go:323] github.com/openshift/origin/pkg/authorization/generated/informers/internalversion/factory.go:45: watch of *api.Role ended with: very short watch May 18 10:23:22 ip-172-31-41-8 atomic-openshift-master: E0518 10:23:22.608983 9701 streamwatcher.go:109] Unable to decode an event from the watch stream: got short buffer with n=0, base=52638, cap=163840 May 18 10:23:22 ip-172-31-41-8 atomic-openshift-master: W0518 10:23:22.609017 9701 reflector.go:323] github.com/openshift/origin/pkg/authorization/generated/informers/internalversion/factory.go:45: watch of *api.ClusterRole ended with: very short watch May 18 10:23:22 ip-172-31-41-8 atomic-openshift-master: E0518 10:23:22.694184 9701 streamwatcher.go:109] Unable to decode an event from the watch stream: got short buffer with n=0, base=5794, cap=16640 May 18 10:23:22 ip-172-31-41-8 atomic-openshift-master: W0518 10:23:22.694221 9701 reflector.go:323] github.com/openshift/origin/pkg/authorization/generated/informers/internalversion/factory.go:45: watch of *api.RoleBinding ended with: very short watch May 18 10:23:22 ip-172-31-41-8 atomic-openshift-master: E0518 10:23:22.978898 9701 streamwatcher.go:109] Unable to decode an event from the watch stream: got short buffer with n=0, base=29172, cap=81920 May 18 10:23:22 ip-172-31-41-8 atomic-openshift-master: W0518 10:23:22.978926 9701 reflector.go:323] github.com/openshift/origin/pkg/authorization/generated/informers/internalversion/factory.go:45: watch of *api.ClusterRoleBinding ended with: very short watch May 18 10:23:22 ip-172-31-41-8 atomic-openshift-master: E0518 10:23:22.996846 9701 streamwatcher.go:109] Unable to decode an event from the watch stream: got short buffer with n=0, base=488, cap=2560 May 18 10:23:22 ip-172-31-41-8 atomic-openshift-master: W0518 10:23:22.996877 9701 reflector.go:323] github.com/openshift/origin/pkg/authorization/generated/informers/internalversion/factory.go:45: watch of *api.Role ended with: very short watch May 18 10:23:23 ip-172-31-41-8 atomic-openshift-master: I0518 10:23:23.124625 9701 rest.go:320] Starting watch for /oapi/v1/egressnetworkpolicies, rv=6 labels= fields= timeout=6m35s May 18 10:23:23 ip-172-31-41-8 atomic-openshift-master: E0518 10:23:23.623052 9701 streamwatcher.go:109] Unable to decode an event from the watch stream: got short buffer with n=0, base=52638, cap=163840 Version-Release number of selected component (if applicable): 3.6.75 How reproducible: Always Steps to Reproduce: 1. Install a 3.6.75 cluster with 1 master + etcd (separate processes), 2 infra and 3 compute nodes on AWS 2. Look in /var/log/messages after successful install Actual results: Error and Warning messages as shown above Expected results: No constant Error messages Additional info: Full master logs attached
Role, ClusterRole, RoleBinding, and ClusterRoleBinding objects do not support watch. They should be returning a 405 method not allowed error instead.
The correct error will be returned by https://github.com/openshift/origin/pull/14260 A separate fix is required to stop the controller that is trying to watch those resources.
https://github.com/openshift/origin/pull/14194 fixes the controller.
Both merged, ON_QA?
Yes
Verified on 3.6.79. Master logs are clean.
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/RHSA-2017:3188