ISO build: staging jobs failure due to: docker allocates port already in use

Bug #1440663 reported by Vitaly Gusev
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Medium
Fuel Library (Deprecated)
6.0.x
Invalid
Undecided
Matthew Mosesohn
7.0.x
Won't Fix
Medium
Bartłomiej Piotrowski

Bug Description

http://jenkins-product.srt.mirantis.net:8080/view/Staging%20Mirrors/job/6.1.staging.iso/229
http://jenkins-product.srt.mirantis.net:8080/view/Staging%20Mirrors/job/6.1.staging.iso/233

http://jenkins-product.srt.mirantis.net:8080/view/Staging%20Mirrors/job/6.1.test_staging_mirror/224/
http://jenkins-product.srt.mirantis.net:8080/view/Staging%20Mirrors/job/6.1.test_staging_mirror/228/

error reading information on service tuned: No such file or directory
error reading information on service avahi-daemon: No such file or directory
error reading information on service iscsi: No such file or directory
error reading information on service iscsid: No such file or directory
error reading information on service firstboot: No such file or directory
error reading information on service kdump: No such file or directory

Preparing bootloader config
error: package ruby is not installed

sudo docker rm -f "fuel-repo-container"
Error response from daemon: No such container: fuel-repo-container
2015/04/05 19:01:01 Error: failed to remove one or more containers
make: [/home/jenkins/workspace/tmp/6.1.staging.iso/build/docker/repo-container-up.done] Error 1 (ignored)
sudo docker -D run -d -p 80 -v /home/jenkins/workspace/tmp/6.1.staging.iso/local_mirror/centos:/var/www/html --name "fuel-repo-container" fuel/centos /usr/sbin/apachectl -DFOREGROUND
027f837698a8a7410c75e16bda22fe244caca7bbaa147ae96058b60f8a0ed662
[debug] commands.go:2229 End of CmdRun(), Waiting for hijack to finish.
2015/04/05 19:01:01 Error response from daemon: Cannot start container 027f837698a8a7410c75e16bda22fe244caca7bbaa147ae96058b60f8a0ed662: Error starting userland proxy: listen tcp 0.0.0.0:49162: bind: address already in use
make: *** [/home/jenkins/workspace/tmp/6.1.staging.iso/build/docker/repo-container-up.done] Error 1
Build step 'Execute shell' marked build as failure

Changed in fuel:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Matthew Mosesohn (raytrac3r)
tags: added: docker
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote : Re: ISO 6.1 staging jobs failure due to: docker allocates port already in use

upstream commit fixes this: https://github.com/docker/docker/pull/9441
upstream bug: https://github.com/docker/docker/issues/8714
We should upgrade to later version of docker on build hosts, preferrably 1.5.0, but 1.4.1 will have this fix as wlel.

summary: - ISO 6.1 staging jobs failure due to: No such container: fuel-repo-
- container
+ ISO 6.1 staging jobs failure due to: docker allocates port already in
+ use
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-main (master)

Fix proposed to branch: master
Review: https://review.openstack.org/170807

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote : Re: ISO 6.1 staging jobs failure due to: docker allocates port already in use

Waiting on reviews. This solution seems to work just fine.

Changed in fuel:
importance: High → Critical
milestone: none → 6.1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-main (master)

Reviewed: https://review.openstack.org/170807
Committed: https://git.openstack.org/cgit/stackforge/fuel-main/commit/?id=3bc810418c9b28246a0f0d8e9f9b29200c9fabf1
Submitter: Jenkins
Branch: master

commit 3bc810418c9b28246a0f0d8e9f9b29200c9fabf1
Author: Matthew Mosesohn <email address hidden>
Date: Mon Apr 6 13:27:37 2015 +0300

    Update lxc-docker to 1.5.0 for iso build

    lxc-docker-1.3.2 has upstream issue
    https://github.com/docker/docker/issues/8714
    which causes failures in allocating ports
    dynamically. Updating resolves this.

    Change-Id: I7fd22591a330ecb4ab0741af9f58fdd4dee54b18
    Closes-Bug: #1440663

Changed in fuel:
status: In Progress → Fix Committed
Changed in fuel:
status: Fix Committed → Fix Released
Revision history for this message
Vasyl Saienko (vsaienko) wrote : Re: ISO 6.1 staging jobs failure due to: docker allocates port already in use
no longer affects: fuel/6.1.x
Revision history for this message
Vasyl Saienko (vsaienko) wrote :
summary: - ISO 6.1 staging jobs failure due to: docker allocates port already in
+ ISO build: staging jobs failure due to: docker allocates port already in
use
Revision history for this message
Sergey Kulanov (skulanov) wrote :

Propose to set to non-critical but high, this is the first case for the last 4 months, checking...

Revision history for this message
Bartłomiej Piotrowski (bpiotrowski) wrote :

Apparently the problem hasn't been completely fixed upstream, looking at: https://github.com/docker/docker/issues/9047

I don't see what can we do about it. All further staging builds finished or failed for different reasons. One option is to retry the command that failed with port taken, but we won't probably see this failure anymore in 4 months.

Revision history for this message
Bartłomiej Piotrowski (bpiotrowski) wrote :

Lowering to medium as it's hard to reproduce.

Dmitry Pyzhov (dpyzhov)
tags: added: area-library
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
assignee: Bartłomiej Piotrowski (bpiotrowski) → Fuel Library Team (fuel-library)
milestone: 7.0 → 8.0
no longer affects: fuel/8.0.x
Dmitry Klenov (dklenov)
Changed in fuel:
status: New → Confirmed
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

This hasn't reproduced in 8.0 yet. Moving to incomplete.

Changed in fuel:
status: Confirmed → Incomplete
Revision history for this message
Roman Prykhodchenko (romcheg) wrote :

Marking as Invalid since it was Incomplete for longer than 3 weeks.

Changed in fuel:
status: Incomplete → 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.