Bug 1482657

Summary:	The current version of kubernetes should not be compiled with golang >= 1.8
Product:	[Fedora] Fedora	Reporter:	Max de Bayser <mbayser>
Component:	kubernetes	Assignee:	Jan Chaloupka <jchaloup>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	26	CC:	eparis, golang-updates, ichavero, jbrooks, jcajka, jchaloup, mbayser, nhorman, tstclair, vbatts
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-29 12:25:00 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 Max de Bayser 2017-08-17 20:05:28 UTC

Description of problem:

Because of a change in the go system library from version 1.8, the kubelet has trouble removing volumes. The issue is described here: https://github.com/kubernetes/kubernetes/issues/43534 . I've rebuilt the fedora 25 golang-1.7 packages on my fedora 26 server to rebuild the kubernetes packages and after that this problem was gone.


Version-Release number of selected component (if applicable):

kubernetes-1.6.7-1

How reproducible:

Always


Steps to Reproduce:

Delete pods with volumes.

Actual results:

The pod will be stuck in Terminating state.

Expected results:

The pod should be removed cleanly

Additional info:

A workaround is to remove the pods from /var/lib/kubelet/pods manually and restart the kubelet

Comment 1 Jan Chaloupka 2017-08-18 09:01:59 UTC

https://github.com/kubernetes/kubernetes/pull/43878 is supposed to resolve the issue. It is present in the lates f26 kubernetes build that is in updates. Can you test it and see if the problem still persists?

https://bodhi.fedoraproject.org/updates/FEDORA-2017-c77d2f6f70

Comment 2 Fedora End Of Life 2018-05-03 08:05:34 UTC

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2018-05-29 12:25:00 UTC

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Max de Bayser 2019-11-07 13:24:31 UTC

No longer relevant.