RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1301199 - docker adds distro tag to docker version which causes kubelet to fail
Summary: docker adds distro tag to docker version which causes kubelet to fail
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1302028
TreeView+ depends on / blocked
 
Reported: 2016-01-22 21:00 UTC by Avesh Agarwal
Modified: 2019-03-06 00:55 UTC (History)
4 users (show)

Fixed In Version: docker-1.9.1-13.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1302028 (view as bug list)
Environment:
Last Closed: 2016-03-31 23:23:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0536 0 normal SHIPPED_LIVE docker bug fix and enhancement update 2016-04-01 03:19:56 UTC

Description Avesh Agarwal 2016-01-22 21:00:17 UTC 
Description of problem:

Due to recent changes in kube upstream (https://github.com/kubernetes/kubernetes/pull/19675), the container run time status is being verified based on docker's Version instead of APIVersion as done before. Since docker on fedora or rhel appends distro string (1.9.1-fc22/el7) to its version, kube parser fails to parse as the last part 1-fc22 is not integer. It was not an issue before as I said because APIVersion was being used which does not have this issue. For example:

$ docker version
Client:
 Version:         1.9.1-fc22
 API version:     1.21
 Package version: docker-1.9.1-4.git64eb95e.fc22.x86_64
 Go version:      go1.5.3
 Git commit:      64eb95e/1.9.1
 Built:
 OS/Arch:         linux/amd64

Server:
 Version:         1.9.1-fc22
 API version:     1.21
 Package version: docker-1.9.1-4.git64eb95e.fc22.x86_64
 Go version:      go1.5.3
 Git commit:      64eb95e/1.9.1
 Built:
 OS/Arch:         linux/amd64

Here are some errors, I noticed on kube nodes:

E0122 10:24:18.435492   27245 manager.go:986] docker: failed to parse docker server version "1.9.1-fc22": Unable to parse version "1.9.1-fc22": "1-fc22" is not an integer
E0122 10:24:23.273679   27245 manager.go:986] docker: failed to parse docker server version "1.9.1-fc22": Unable to parse version "1.9.1-fc22": "1-fc22" is not an integer
E0122 10:24:23.273692   27245 kubelet.go:2579] Container runtime sanity check failed: docker: failed to parse docker server version "1.9.1-fc22": Unable to parse version "1.9.1-fc22": "1-fc22" is not an integer

Detailed logs: http://pastebin.test.redhat.com/342892

As container run time status fails, all nodes in kube cluster are going down from Ready to NotReady status (it takes almost 5m in my setup). 


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

How reproducible:
always

Steps to Reproduce:
1. git clone kubernetes which has https://github.com/kubernetes/kubernetes/pull/19675
2. cd kubernetes
3. make clean all
4. ./hack/local-up-cluster.sh
5. kubectl get nodes (wait for around 5 or more mins and see node status changes to NotReady
6. check kubelet logs: cat /tmp/kubelet.log and notice errors regarding 1-fc22 or 1-el7 not an integer.

 

Actual results:
docker version shows Version as 1.9.1-fc22/el7

Expected results:
docker version shows Version as 1.9.1


Additional info:
Comment 3 Daniel Walsh 2016-01-26 14:40:06 UTC 
This is now beleived to be a kubernetes bug.  It should be able to handle the version.
Comment 4 Jan Chaloupka 2016-01-26 14:56:01 UTC 
I see there is a temporary fix in docker. Not blocker for 7.2.2.
Comment 5 Jan Chaloupka 2016-01-26 15:03:46 UTC 
Switching back to docker component as this bug is already attached in erratum.
Comment 6 Luwen Su 2016-03-17 19:03:02 UTC 
In 
kubernetes-1.2.0-0.9.alpha1.gitb57e8bd.el7.x86_64
docker-1.9.1-23.el7.x86_64

The docker version is shown correct, move to vierfied
kubelet: I0318 03:00:26.036165   29134 manager.go:169] Version: {KernelVersion:3.10.0-294.el7.x86_64 ContainerOsVersion:Red Hat Enterprise Linux DockerVersion:1.9.1 CadvisorVersion: CadvisorRevision:
Comment 8 errata-xmlrpc 2016-03-31 23:23:32 UTC 
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://rhn.redhat.com/errata/RHBA-2016-0536.html
Note You need to log in before you can comment on or make changes to this bug.