OpenStack Compute (nova)

[Docker] The nova network device (pvnetXXX) is lost after a instance soft/hard reboot

Bug #1256256 reported by Daniel Kuffner
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned
nova-docker
Fix Committed
Undecided
Unassigned

Bug Description

The nova docker driver doesn't seem to handle a reboot correctly.
A docker container which has been started via nova has a network device pvnetXXX which belongs to the nova network.
This network device is lost after a instance reboot

Tags: docker
Gary Kotton (garyk)
tags: added: docker
Revision history for this message
damitha kumarage (damitha) wrote :

I have the same issue. I run Ubuntu13.04 on virtualbox with docker 0.7.2 version.

Erica Windisch (ewindisch)
Changed in nova:
status: New → Invalid
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova-docker (master)

Reviewed: https://review.openstack.org/104271
Committed: https://git.openstack.org/cgit/stackforge/nova-docker/commit/?id=999de7646a9e41c3e97ff853411ba31ec8733796
Submitter: Jenkins
Branch: master

commit 999de7646a9e41c3e97ff853411ba31ec8733796
Author: João Paulo Barraca <email address hidden>
Date: Thu Jul 10 17:01:41 2014 +0100

    Restablish networking upon container reboot

    Currently, whenever a container is rebooted, it will
    lose its IP address.

    This happens because a container's ID and PID will change, while the
    namespaces are mapped to both.

    This fix unplugs and replugs networking between stopping and
    starting of the container.

    Closes-Bug: #1256256

    Change-Id: I583926e43c832605c77852205b4e2df8ce9746ed

Changed in nova-docker:
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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