'phys' interface does not come back after lxc-stop

Bug #1086244 reported by Avijit Ghosh
22
This bug affects 6 people
Affects Status Importance Assigned to Milestone
lxc (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Running 'lxc 0.7.5-3ubuntu65' on 12.04.1 LTS [Precise Pangolin]

Created a container with lxc.network.type=phys. I start the container [ok], stop the container [ok], start the container again -- it fails with error message 'Failed to retrieve index for eth1'. Turns our 'eth1' was renamed 'dev3' and was not renamed back.

This is actually the same problem as bug #764278 -- only bug #764278 was reported for Lucid and I am getting it on Precise kernel version 3.2.0-29-generic-pae. For #764278, it was marked 'invalid' with reason 'lxc isn't supported on lucid' and 'is fixed in newer kernels. Apparently not.

Tags: lxc lxc-stop phys
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

(Note that if lxc.network.name is not specified (or is the same as lxc.network.link) then this doesn't happen, which is a workaround for this)

There is currently no code in lxc renaming the nics at container shutdown. That needs to be added.

Changed in lxc (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
description: updated
summary: - lxc-stop on precise: 'phys' interface does not come back after lxc-stop
+ 'phys' interface does not come back after lxc-stop
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

This has been fixed in the upstream staging tree. The fix should be merged into raring as soon as 0.9.0 is released and merged.

Changed in lxc (Ubuntu):
status: Triaged → Fix Committed
Changed in lxc (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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