Red Hat Bugzilla – Bug 1347425
Logs filled with errors after deleting project
Last modified: 2016-09-27 05:34:13 EDT
Created attachment 1168827 [details] Logs from /var/log/messages Description of problem: Logs are filled with following errors when deleting a project Jun 16 15:44:44 ip-172-31-8-173 atomic-openshift-master: E0616 15:44:44.369096 11084 endpoints_controller.go:443] Error updating endpoints: endpoints "dancer-example" is forbidden: Unable to create new content in namespace test1 because it is being terminated. Version-Release number of selected component (if applicable): openshift v3.2.1.2-1-g64665fc kubernetes v1.2.0-36-g4a3f9c5 etcd 2.2.5 root@ip-172-31-8-173: ~ # docker version Client: Version: 1.10.3 API version: 1.22 Package version: docker-common-1.10.3-42.el7.x86_64 Go version: go1.4.2 Git commit: 02f13c2-unsupported Built: Mon Jun 13 15:22:15 2016 OS/Arch: linux/amd64 Server: Version: 1.10.3 API version: 1.22 Package version: docker-common-1.10.3-42.el7.x86_64 Go version: go1.4.2 Git commit: 02f13c2-unsupported Built: Mon Jun 13 15:22:15 2016 OS/Arch: linux/amd64 How reproducible: Frequently Steps to Reproduce: 1. Create a new project 2. Create a new app using available templates (cakephp-mysql-example) 3. Delete a project Actual results: Logs are filled with attached errors Expected results: Logs should be clean. Additional info:
Does project deletion cause creation of any resource? We are not trying to create anything while deleting the project.
This issue might be related to https://bugzilla.redhat.com/show_bug.cgi?id=1333393
Upstream logging fix: https://github.com/kubernetes/kubernetes/pull/30510
Origin cherry-pick: https://github.com/openshift/origin/pull/10415
verified in following release, do not see these messages openshift v3.3.0.23 kubernetes v1.3.0+507d3a7 etcd 2.3.0+git
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-2016:1933