centos:kilo:R3.1 build 56: docker fails to start with "docker: Error response from daemon: mkdir /var/lib/docker/overlay/fa6ec3f9d4beed29cbe71b61ab2ce632d67a7cd97c98f9f1e9eb5cbaf57b6613-init/merged/dev/shm: invalid argument."

Bug #1658002 reported by sundarkh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Invalid
Undecided
Unassigned
R3.1
Invalid
Medium
Jeba Paulaiyan

Bug Description

centos:kilo:R3.1 build 56: docker fails to start with "docker: Error response from daemon: mkdir /var/lib/docker/overlay/fa6ec3f9d4beed29cbe71b61ab2ce632d67a7cd97c98f9f1e9eb5cbaf57b6613-init/merged/dev/shm: invalid argument."

1) Centos R3.1 build 56, docker fails to inititialise with docker fails to start with "docker: Error response from daemon: mkdir /var/lib/docker/overlay/fa6ec3f9d4beed29cbe71b61ab2ce632d67a7cd97c98f9f1e9eb5cbaf57b6613-init/merged/dev/shm: invalid argument."

sample runs which hit this issue

http://anamika.englab.juniper.net:8080/job/ServerManager_centos-7-1_kilo_multi_node_Sanity/20/console
http://anamika.englab.juniper.net:8080/job/ServerManager_centos-7-1_kilo_Multi_Interface_Sanity/24/console

2) hkumark pointed out

  I mentioned before it seems you are hitting the bug https://github.com/docker/docker/issues/10294

The conditions seems same as mentioned in the bug, so may be you would have to try

try upgrading kernel and see xfs issue has been fixed
Try ext4 filesystem rather than xfs which don’t have this problem
Try using a different machine to install contrail-test containers

Notes
-----
1) till R3.1 build 53, this issue was not seen; build 55, saw it once, from build 56 consistently seeing

2) Need a solution on making the centos docker for kilo to work

Tags: automation
Revision history for this message
Jeba Paulaiyan (jebap) wrote :

This need to be handled by setting up separate test node in Sanity.

Jeba Paulaiyan (jebap)
tags: removed: blocker sanity
tags: added: automation
Revision history for this message
Jeba Paulaiyan (jebap) wrote :

This is not related to contrail code. This happened because we pull latest docker from upstream always and there was a bug in the upstream docker during this bug.

Changed in juniperopenstack:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.