error synchronizing: clusterrole.rbac.authorization.k8s.io "aggregated-apiserver-clusterrole" not found

[wking]

@RobertKrawitz is seeing:

Warning Unhealthy 39m kubelet, dev1-master-0 Readiness probe failed: Get https://10.2.0.19:8443/healthz: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Warning Unhealthy 38m kubelet, dev1-master-0 Readiness probe failed: HTTP probe failed with statuscode: 500
E1017 15:21:07.774244 1 cache.go:332] error synchronizing: clusterrole.rbac.authorization.k8s.io "aggregated-apiserver-clusterrole" not found

in the apiserver pod in the openshift-apiserver namespace using openshift-install v0.2.0-23-g079fe51f8f6b4e9ec5f084e620d1adf13c0adbe5 (I dunno what cluster-opernshift-apiserver-operator image) on libvirt. Is this a known issue?

[deads2k]

@RobertKrawitz can we get a gist of a log dump and the yaml output for your apiserver pod? We know there's a bad rolebinding somewhere, but the "normal" symptom is a log message and no other effect.

[RobertKrawitz]

I'll fire it up but probably won't have a dump until later this afternoon.

[RobertKrawitz]

Attached are the pod description, pod YAML, and pod logs. The logs are compacted by eliding duplicate lines and printing the number of reps in (parentheses) after the line.

I will keep the cluster up for now in case you want more info.

apiserver.desc.txt
apiserver.yaml.txt
apiserver-logs.txt

[RobertKrawitz]

I can no longer reproduce this.

[smarterclayton]

I'm still seeing this on todays clusters

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.