Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1462336 - Inactive controller-managers are complain about old resource versions for secrets
Inactive controller-managers are complain about old resource versions for sec...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Pod (Show other bugs)
3.5.1
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: David Eads
Weihua Meng
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-16 14:55 EDT by Eric Paris
Modified: 2017-08-16 15 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-10 01:28:09 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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1716 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.6 RPM Release Advisory 2017-08-10 05:02:50 EDT

  None (edit)
Description Eric Paris 2017-06-16 14:55:37 EDT
oc v3.5.5.19

We have a 3 master cluster so 2 of the controller-managers are inactive.

Approximately every 1:20 both of the inactive controller manager print:

Jun 16 18:53:24 ip-X-X-X-X.ec2.internal atomic-openshift-master-controllers[51817]: W0616 18:53:24.085007   51817 reflector.go:319] github.com/openshift/origin/vendor/k8s.io/kubernetes/plugin/pkg/admission/serviceaccount/admission.go:119: watch of *api.Secret ended with: too old resource version: 557199129 (557207180)


Why are the controller managers watching secrets when they are inactive? Why are they complaining about something that could be so normal? These are run with:

/usr/bin/openshift start master controllers --config=/etc/origin/master/master-config.yaml --loglevel=2 --listen=https://0.0.0.0:8444
Comment 1 Derek Carr 2017-06-16 15:05:07 EDT
i am confused, this is an admission controller being used in controller-manager?
Comment 2 Jordan Liggitt 2017-06-21 10:48:35 EDT
Addressed by https://github.com/openshift/origin/pull/14775
Comment 4 Weihua Meng 2017-07-06 05:32:53 EDT
verified on openshift v3.6.135
those message are not found.
move to verified.
Comment 6 errata-xmlrpc 2017-08-10 01:28:09 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/RHEA-2017:1716

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