2012-04-02 15:16:28 |
Eric Dodemont |
bug |
|
|
added bug |
2012-04-02 15:17:36 |
Eric Dodemont |
description |
When I launch more than one LXC instance, and I try to delete one (the first one for example), the wrong rootfs is umounted and disconnected from its nbd device (the last one for example).
E.g.
Before:
name status nbd --> rootfs_path veth_if --> IP cgroup
----------------------------------------------------------------------------------------------------------------------------
instance1 ACTIVE nbd15 --> .../instance-00000001/rootfs veth0 --> 10.0.0.2 V
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 ACTIVE nbd13 --> .../instance-00000003/rootfs veth2 --> 10.0.0.4 V
nova delete instance1
After:
name status nbd --> rootfs_path veth_if --> IP cgroup
----------------------------------------------------------------------------------------------------------------------------
instance1 SHUTOFF nbd15 --> .../instance-00000001/rootfs X --> X X
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 ACTIVE X --> X veth2 --> 10.0.0.4 V
Specifications:
- Host: KVM VM
- Host OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- Guest OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- OpenStack version: folsom-1 (but probably exact same behavior with essex-rc1) from github master branch with devstack
- Virtualization: LXC (LinuX Container) |
When I launch more than one LXC instance, and I try to delete one (the first one for example), the wrong rootfs is umounted and disconnected from its nbd device (the last one for example).
E.g.
Before:
name status nbd --> rootfs_path veth_if --> IP group
---------------------------------------------------------------------------------------
instance1 ACTIVE nbd15 --> .../instance-00000001/rootfs veth0 --> 10.0.0.2 V
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 ACTIVE nbd13 --> .../instance-00000003/rootfs veth2 --> 10.0.0.4 V
nova delete instance1
After:
name status nbd --> rootfs_path veth_if --> IP group
---------------------------------------------------------------------------------------
instance1 SHUTOFF nbd15 --> .../instance-00000001/rootfs X --> X X
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 ACTIVE X --> X veth2 --> 10.0.0.4 V
Specifications:
- Host: KVM VM
- Host OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- Guest OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- OpenStack version: folsom-1 (but probably exact same behavior with essex-rc1) from github master branch with devstack
- Virtualization: LXC (LinuX Container) |
|
2012-04-02 15:18:45 |
Eric Dodemont |
description |
When I launch more than one LXC instance, and I try to delete one (the first one for example), the wrong rootfs is umounted and disconnected from its nbd device (the last one for example).
E.g.
Before:
name status nbd --> rootfs_path veth_if --> IP group
---------------------------------------------------------------------------------------
instance1 ACTIVE nbd15 --> .../instance-00000001/rootfs veth0 --> 10.0.0.2 V
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 ACTIVE nbd13 --> .../instance-00000003/rootfs veth2 --> 10.0.0.4 V
nova delete instance1
After:
name status nbd --> rootfs_path veth_if --> IP group
---------------------------------------------------------------------------------------
instance1 SHUTOFF nbd15 --> .../instance-00000001/rootfs X --> X X
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 ACTIVE X --> X veth2 --> 10.0.0.4 V
Specifications:
- Host: KVM VM
- Host OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- Guest OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- OpenStack version: folsom-1 (but probably exact same behavior with essex-rc1) from github master branch with devstack
- Virtualization: LXC (LinuX Container) |
When I launch more than one LXC instance, and I try to delete one (the first one for example), the wrong rootfs is umounted and disconnected from its nbd device (the last one for example).
E.g.
Before:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 ACTIVE nbd15 --> .../instance-00000001/rootfs veth0 --> 10.0.0.2 V
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 ACTIVE nbd13 --> .../instance-00000003/rootfs veth2 --> 10.0.0.4 V
nova delete instance1
After:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 SHUTOFF nbd15 --> .../instance-00000001/rootfs X --> X X
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 ACTIVE X --> X veth2 --> 10.0.0.4 V
Specifications:
- Host: KVM VM
- Host OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- Guest OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- OpenStack version: folsom-1 (but probably exact same behavior with essex-rc1) from github master branch with devstack
- Virtualization: LXC (LinuX Container) |
|
2012-04-03 08:13:47 |
Eric Dodemont |
description |
When I launch more than one LXC instance, and I try to delete one (the first one for example), the wrong rootfs is umounted and disconnected from its nbd device (the last one for example).
E.g.
Before:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 ACTIVE nbd15 --> .../instance-00000001/rootfs veth0 --> 10.0.0.2 V
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 ACTIVE nbd13 --> .../instance-00000003/rootfs veth2 --> 10.0.0.4 V
nova delete instance1
After:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 SHUTOFF nbd15 --> .../instance-00000001/rootfs X --> X X
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 ACTIVE X --> X veth2 --> 10.0.0.4 V
Specifications:
- Host: KVM VM
- Host OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- Guest OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- OpenStack version: folsom-1 (but probably exact same behavior with essex-rc1) from github master branch with devstack
- Virtualization: LXC (LinuX Container) |
When I launch more than one LXC instance, and I try to delete one (the first one for example), the wrong rootfs is umounted and disconnected from its nbd device (the last one for example).
E.g.
Before:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 ACTIVE nbd15 --> .../instance-00000001/rootfs veth0 --> 10.0.0.2 V
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 ACTIVE nbd13 --> .../instance-00000003/rootfs veth2 --> 10.0.0.4 V
nova delete instance1
After:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 SHUTOFF nbd15 --> .../instance-00000001/rootfs X --> X X
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 SHUTOFF X --> X veth2 --> 10.0.0.4 V
Specifications:
- Host: KVM VM
- Host OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- Guest OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- OpenStack version: folsom-1 (but probably exact same behavior with essex-rc1) from github master branch with devstack
- Virtualization: LXC (LinuX Container) |
|
2012-04-03 08:14:40 |
Eric Dodemont |
description |
When I launch more than one LXC instance, and I try to delete one (the first one for example), the wrong rootfs is umounted and disconnected from its nbd device (the last one for example).
E.g.
Before:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 ACTIVE nbd15 --> .../instance-00000001/rootfs veth0 --> 10.0.0.2 V
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 ACTIVE nbd13 --> .../instance-00000003/rootfs veth2 --> 10.0.0.4 V
nova delete instance1
After:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 SHUTOFF nbd15 --> .../instance-00000001/rootfs X --> X X
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 SHUTOFF X --> X veth2 --> 10.0.0.4 V
Specifications:
- Host: KVM VM
- Host OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- Guest OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- OpenStack version: folsom-1 (but probably exact same behavior with essex-rc1) from github master branch with devstack
- Virtualization: LXC (LinuX Container) |
When I launch more than one LXC instance, and I try to delete one (the first one for example), the wrong rootfs is umounted and disconnected from its nbd device (the last one for example).
E.g.
Before:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 ACTIVE nbd15 --> .../instance-00000001/rootfs veth0 --> 10.0.0.2 V
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 ACTIVE nbd13 --> .../instance-00000003/rootfs veth2 --> 10.0.0.4 V
nova delete instance1
After:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 SHUTOFF nbd15 --> .../instance-00000001/rootfs X --> X X
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 SHUTOFF X --> X veth2 --> 10.0.0.4 X
Specifications:
- Host: KVM VM
- Host OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- Guest OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- OpenStack version: folsom-1 (but probably exact same behavior with essex-rc1) from github master branch with devstack
- Virtualization: LXC (LinuX Container) |
|
2012-04-06 11:01:06 |
Eric Dodemont |
description |
When I launch more than one LXC instance, and I try to delete one (the first one for example), the wrong rootfs is umounted and disconnected from its nbd device (the last one for example).
E.g.
Before:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 ACTIVE nbd15 --> .../instance-00000001/rootfs veth0 --> 10.0.0.2 V
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 ACTIVE nbd13 --> .../instance-00000003/rootfs veth2 --> 10.0.0.4 V
nova delete instance1
After:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 SHUTOFF nbd15 --> .../instance-00000001/rootfs X --> X X
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 SHUTOFF X --> X veth2 --> 10.0.0.4 X
Specifications:
- Host: KVM VM
- Host OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- Guest OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- OpenStack version: folsom-1 (but probably exact same behavior with essex-rc1) from github master branch with devstack
- Virtualization: LXC (LinuX Container) |
When I launch more than one LXC instance, and I try to delete one (the first one for example), the wrong rootfs is umounted and disconnected from its nbd device (the last one for example).
E.g.
Before:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 ACTIVE nbd15 --> .../instance-00000001/rootfs veth0 --> 10.0.0.2 V
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 ACTIVE nbd13 --> .../instance-00000003/rootfs veth2 --> 10.0.0.4 V
nova delete instance1
After:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 SHUTOFF nbd15 --> .../instance-00000001/rootfs X --> X X
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 SHUTOFF X --> X veth2 --> 10.0.0.4 X
Specifications:
- Host: KVM VM
- Host OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- Guest OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- OpenStack version: 2012.1 (essex)
- Virtualization: LXC (LinuX Container) |
|
2012-04-06 11:02:04 |
Eric Dodemont |
description |
When I launch more than one LXC instance, and I try to delete one (the first one for example), the wrong rootfs is umounted and disconnected from its nbd device (the last one for example).
E.g.
Before:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 ACTIVE nbd15 --> .../instance-00000001/rootfs veth0 --> 10.0.0.2 V
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 ACTIVE nbd13 --> .../instance-00000003/rootfs veth2 --> 10.0.0.4 V
nova delete instance1
After:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 SHUTOFF nbd15 --> .../instance-00000001/rootfs X --> X X
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 SHUTOFF X --> X veth2 --> 10.0.0.4 X
Specifications:
- Host: KVM VM
- Host OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- Guest OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- OpenStack version: 2012.1 (essex)
- Virtualization: LXC (LinuX Container) |
When I launch more than one LXC instance, and I try to delete one (the first one for example), the wrong rootfs is umounted and disconnected from its nbd device (the last one for example).
E.g.
Before:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 ACTIVE nbd15 --> .../instance-00000001/rootfs veth0 --> 10.0.0.2 V
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 ACTIVE nbd13 --> .../instance-00000003/rootfs veth2 --> 10.0.0.4 V
nova delete instance1
After:
name status nbd --> rootfs_path veth_if --> IP cgroup
---------------------------------------------------------------------------------------
instance1 SHUTOFF nbd15 --> .../instance-00000001/rootfs X --> X X
instance2 ACTIVE nbd14 --> .../instance-00000002/rootfs veth1 --> 10.0.0.3 V
instance3 SHUTOFF X --> X veth2 --> 10.0.0.4 X
Specifications:
- Host OS: ubuntu precise beta2
- Guest OS: ubuntu precise beta2 cloud image (from http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64.tar.gz)
- OpenStack version: 2012.1 (essex)
- Virtualization: LXC (LinuX Container) |
|
2012-04-13 09:34:26 |
Tom Ellis |
bug |
|
|
added subscriber Tom Ellis |
2012-04-21 09:10:00 |
Russell Bryant |
nova: status |
New |
Confirmed |
|
2012-04-21 09:10:03 |
Russell Bryant |
nova: importance |
Undecided |
High |
|
2012-04-28 18:08:54 |
Patrick Hetu |
bug |
|
|
added subscriber Patrick Hetu |
2012-06-20 09:12:51 |
Thierry Carrez |
tags |
|
lxc |
|
2012-07-11 04:20:39 |
Muharem Hrnjadovic |
nova: assignee |
|
Muharem Hrnjadovic (al-maisan) |
|
2012-07-11 04:20:50 |
Muharem Hrnjadovic |
nova: status |
Confirmed |
In Progress |
|
2012-07-24 10:07:27 |
Muharem Hrnjadovic |
nova: assignee |
Muharem Hrnjadovic (al-maisan) |
|
|
2012-07-24 10:07:32 |
Muharem Hrnjadovic |
nova: status |
In Progress |
Confirmed |
|
2012-07-27 15:54:54 |
Pádraig Brady |
nova: assignee |
|
Pádraig Brady (p-draigbrady) |
|
2012-08-01 14:50:14 |
OpenStack Infra |
nova: status |
Confirmed |
In Progress |
|
2012-08-04 03:50:20 |
OpenStack Infra |
nova: status |
In Progress |
Fix Committed |
|
2012-08-07 14:58:15 |
Pádraig Brady |
nominated for series |
|
nova/essex |
|
2012-08-07 14:58:15 |
Pádraig Brady |
bug task added |
|
nova/essex |
|
2012-08-07 14:58:29 |
Pádraig Brady |
nova/essex: assignee |
|
Pádraig Brady (p-draigbrady) |
|
2012-08-07 14:58:34 |
Pádraig Brady |
nova/essex: importance |
Undecided |
High |
|
2012-08-07 14:58:42 |
Pádraig Brady |
nova/essex: milestone |
|
2012.1.2 |
|
2012-08-07 14:58:44 |
Pádraig Brady |
nova: milestone |
|
folsom-3 |
|
2012-08-07 22:33:34 |
Mark McLoughlin |
nova/essex: status |
New |
In Progress |
|
2012-08-07 22:47:04 |
Mark McLoughlin |
nova/essex: milestone |
2012.1.2 |
|
|
2012-08-16 07:32:01 |
Thierry Carrez |
nova: status |
Fix Committed |
Fix Released |
|
2012-08-21 14:47:35 |
OpenStack Infra |
nova/essex: status |
In Progress |
Fix Committed |
|
2012-08-24 09:15:38 |
Dave Walker |
nova (Ubuntu): status |
New |
Fix Released |
|
2012-08-24 09:15:42 |
Dave Walker |
nominated for series |
|
Ubuntu Precise |
|
2012-08-24 09:15:43 |
Dave Walker |
bug task added |
|
nova (Ubuntu Precise) |
|
2012-08-24 09:15:45 |
Dave Walker |
nova (Ubuntu Precise): status |
New |
Confirmed |
|
2012-08-24 09:51:36 |
Launchpad Janitor |
branch linked |
|
lp:~openstack-ubuntu-testing/nova/precise-essex-proposed |
|
2012-08-24 19:45:23 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/precise-proposed/nova |
|
2012-08-30 07:34:49 |
Adam Gandelman |
attachment added |
|
2012.1.3+stable-20120827-4d2a4afe-0ubuntu1.log https://bugs.launchpad.net/bugs/971621/+attachment/3283212/+files/2012.1.3%2Bstable-20120827-4d2a4afe-0ubuntu1.log |
|
2012-08-30 07:34:52 |
Adam Gandelman |
tags |
lxc |
lxc verification-done |
|
2012-09-03 15:18:08 |
Launchpad Janitor |
nova (Ubuntu Precise): status |
Confirmed |
Fix Released |
|
2012-09-03 15:18:08 |
Launchpad Janitor |
cve linked |
|
2012-3360 |
|
2012-09-03 15:18:08 |
Launchpad Janitor |
cve linked |
|
2012-3361 |
|
2012-09-03 15:18:08 |
Launchpad Janitor |
cve linked |
|
2012-3371 |
|
2012-09-03 15:18:08 |
Launchpad Janitor |
cve linked |
|
2012-3447 |
|
2012-09-27 15:25:21 |
Thierry Carrez |
nova: milestone |
folsom-3 |
2012.2 |
|
2012-10-09 19:52:13 |
Mark McLoughlin |
nova/essex: milestone |
|
2012.1.3 |
|
2012-10-11 19:44:13 |
Mark McLoughlin |
nova/essex: status |
Fix Committed |
Fix Released |
|