2008-04-13 12:21:50 |
Carl Fooks |
bug |
|
|
added bug |
2008-04-13 12:21:50 |
Carl Fooks |
bug |
|
|
added attachment 'xendomains.patch' (xendomains.patch) |
2008-08-21 20:07:43 |
Ian Taylor |
bug |
|
|
added attachment 'xendomains.patch' (Fixes some problems with paths in /etc/default/xendomains containing spaces. Fixes 'cut cut' issue. Contains one-liner zombie patch.) |
2008-11-12 06:50:54 |
Evan Broder |
bug |
|
|
added subscriber XVM developers |
2008-11-12 06:53:56 |
Evan Broder |
xen-3.2: status |
New |
Confirmed |
|
2008-11-12 06:53:56 |
Evan Broder |
xen-3.2: statusexplanation |
|
|
|
2008-12-06 16:47:02 |
Evan Broder |
description |
The xendomains init script has a couple of errors, that while not fatal are annoying!
I've attached a patch file to fix the two that were bothering me.
Please note, this is not the same as bug #208300. |
The xendomains init script has a couple of errors.
These errors cause the normal migrate then save then shutdown mechanisms to fail, and instead skip straight to the "shutdown all" stage, which is a major departure from the expected behavior.
The attached patch from Carl Fooks (http://launchpadlibrarian.net/13407539/xendomains.patch) represents the minimal patch necessary to restore functionality.
Details to reproduce:
1. Start a Xen domU
2. Run /etc/init.d/xendomains stop
3. Observe that, after several errors are spewed, the domU is not saved to /var/lib/xen/save, as is the default Ubuntu config, but is instead shutdown.
Please note, this is not the same as bug #208300. |
|
2008-12-06 16:47:42 |
Evan Broder |
bug |
|
|
added subscriber MOTU Stable Release Updates |
2008-12-06 16:49:57 |
Evan Broder |
description |
The xendomains init script has a couple of errors.
These errors cause the normal migrate then save then shutdown mechanisms to fail, and instead skip straight to the "shutdown all" stage, which is a major departure from the expected behavior.
The attached patch from Carl Fooks (http://launchpadlibrarian.net/13407539/xendomains.patch) represents the minimal patch necessary to restore functionality.
Details to reproduce:
1. Start a Xen domU
2. Run /etc/init.d/xendomains stop
3. Observe that, after several errors are spewed, the domU is not saved to /var/lib/xen/save, as is the default Ubuntu config, but is instead shutdown.
Please note, this is not the same as bug #208300. |
Binary package hint: xen-utils-3.2
The xendomains init script has a couple of errors.
These errors cause the normal migrate then save then shutdown mechanisms to fail, and instead skip straight to the "shutdown all" stage, which is a major departure from the expected behavior.
The attached patch from Carl Fooks (http://launchpadlibrarian.net/13407539/xendomains.patch) represents the minimal patch necessary to restore functionality.
Details to reproduce:
1. Start a Xen domU
2. Run /etc/init.d/xendomains stop
3. Observe that, after several errors are spewed, the domU is not saved to /var/lib/xen/save, as is the default Ubuntu config, but is instead shutdown.
Please note, this is not the same as bug #208300. |
|
2008-12-07 13:21:37 |
Evan Broder |
description |
Binary package hint: xen-utils-3.2
The xendomains init script has a couple of errors.
These errors cause the normal migrate then save then shutdown mechanisms to fail, and instead skip straight to the "shutdown all" stage, which is a major departure from the expected behavior.
The attached patch from Carl Fooks (http://launchpadlibrarian.net/13407539/xendomains.patch) represents the minimal patch necessary to restore functionality.
Details to reproduce:
1. Start a Xen domU
2. Run /etc/init.d/xendomains stop
3. Observe that, after several errors are spewed, the domU is not saved to /var/lib/xen/save, as is the default Ubuntu config, but is instead shutdown.
Please note, this is not the same as bug #208300. |
Binary package hint: xen-utils-3.2
The xendomains init script has a couple of errors.
IMPACT: These errors cause the normal migrate then save then shutdown mechanisms to fail, and instead skip straight to the "shutdown all" stage. In addition to being a major departure from the expected behavior, this could cause loss of user data, if users expect the state of their VMs to be saved instead of destroyed.
PATCH: The attached patch from Carl Fooks (http://launchpadlibrarian.net/13407539/xendomains.patch) represents the minimal patch necessary to restore functionality.
TEST CASE:
1. Start a Xen domU
2. Run /etc/init.d/xendomains stop
3. Observe that, after several errors are spewed, the domU is not saved to /var/lib/xen/save, as is the default Ubuntu config, but is instead shutdown.
REGRESSIONS: This is a two line patch whose implications can be pretty easily observed directly. It is highly unlikely to make things any less functional than they are now.
Please note, this is not the same as bug #208300. |
|
2008-12-07 13:37:58 |
Evan Broder |
bug |
|
|
assigned to xen-3.3 (Ubuntu) |
2008-12-13 17:40:00 |
Evan Broder |
bug |
|
|
added attachment 'xen-3.3_3.3.0-1ubuntu8.debdiff' (xen-3.3_3.3.0-1ubuntu8.debdiff) |
2008-12-13 17:41:00 |
Evan Broder |
bug |
|
|
added subscriber Ubuntu Sponsors for main |
2008-12-13 18:42:47 |
Evan Broder |
bug |
|
|
added attachment 'xen-3.3_3.3.0-1ubuntu8.debdiff' (xen-3.3_3.3.0-1ubuntu8.debdiff) |
2008-12-16 02:48:36 |
Bryce Harrington |
xen-3.3: status |
New |
Fix Committed |
|
2008-12-16 02:48:36 |
Bryce Harrington |
xen-3.3: statusexplanation |
|
Thanks; sponsored! |
|
2008-12-16 02:50:06 |
Launchpad Janitor |
xen-3.3: status |
Fix Committed |
Fix Released |
|
2008-12-16 03:34:39 |
Evan Broder |
bug |
|
|
added attachment 'xen-3.2_3.2.0-0ubuntu11.debdiff' (xen-3.2_3.2.0-0ubuntu11.debdiff) |
2008-12-16 03:35:19 |
Evan Broder |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2008-12-16 03:38:02 |
Evan Broder |
description |
Binary package hint: xen-utils-3.2
The xendomains init script has a couple of errors.
IMPACT: These errors cause the normal migrate then save then shutdown mechanisms to fail, and instead skip straight to the "shutdown all" stage. In addition to being a major departure from the expected behavior, this could cause loss of user data, if users expect the state of their VMs to be saved instead of destroyed.
PATCH: The attached patch from Carl Fooks (http://launchpadlibrarian.net/13407539/xendomains.patch) represents the minimal patch necessary to restore functionality.
TEST CASE:
1. Start a Xen domU
2. Run /etc/init.d/xendomains stop
3. Observe that, after several errors are spewed, the domU is not saved to /var/lib/xen/save, as is the default Ubuntu config, but is instead shutdown.
REGRESSIONS: This is a two line patch whose implications can be pretty easily observed directly. It is highly unlikely to make things any less functional than they are now.
Please note, this is not the same as bug #208300. |
Binary package hint: xen-utils-3.2
The xendomains init script has a couple of errors.
IMPACT: These errors cause the normal migrate then save then shutdown mechanisms to fail, and instead skip straight to the "shutdown all" stage. In addition to being a major departure from the expected behavior, this could cause loss of user data, if users expect the state of their VMs to be saved instead of destroyed.
PATCH: http://launchpadlibrarian.net/20457983/xen-3.2_3.2.0-0ubuntu11.debdiff for Hardy and http://launchpadlibrarian.net/20406413/xen-3.3_3.3.0-1ubuntu8.debdiff for Intrepid represent the minimal patch to restore functionality.
TEST CASE:
1. Start a Xen domU
2. Run /etc/init.d/xendomains stop
3. Observe that, after several errors are spewed, the domU is not saved to /var/lib/xen/save, as is the default Ubuntu config, but is instead shutdown.
REGRESSIONS: This is a two line patch whose implications can be pretty easily observed directly. It is highly unlikely to make things any less functional than they are now.
Please note, this is not the same as bug #208300. |
|
2008-12-16 04:19:49 |
Martin Pitt |
xen-3.3: status |
New |
Invalid |
|
2008-12-16 04:19:49 |
Martin Pitt |
xen-3.3: statusexplanation |
|
|
|
2008-12-16 04:20:27 |
Martin Pitt |
xen-3.3: status |
New |
Confirmed |
|
2008-12-16 04:20:27 |
Martin Pitt |
xen-3.3: statusexplanation |
|
Looks fine for an SRU. Bryce, mind sponsoring those, too? |
|
2008-12-16 04:20:38 |
Martin Pitt |
xen-3.2: status |
Confirmed |
Invalid |
|
2008-12-16 04:20:38 |
Martin Pitt |
xen-3.2: statusexplanation |
|
|
|
2008-12-16 04:20:50 |
Martin Pitt |
xen-3.2: status |
New |
Invalid |
|
2008-12-16 04:20:50 |
Martin Pitt |
xen-3.2: statusexplanation |
|
|
|
2008-12-16 04:21:03 |
Martin Pitt |
xen-3.2: status |
New |
Confirmed |
|
2008-12-16 04:21:03 |
Martin Pitt |
xen-3.2: statusexplanation |
|
|
|
2009-01-29 20:42:27 |
Evan Broder |
bug |
|
|
added subscriber Bryce Harrington |
2009-02-19 19:22:14 |
Martin Pitt |
xen-3.2: status |
Confirmed |
Fix Committed |
|
2009-02-24 21:29:18 |
Evan Broder |
bug |
|
|
added attachment 'xen-3.3_3.3.0-1ubuntu7.1.debdiff' (xen-3.3_3.3.0-1ubuntu7.1.debdiff) |
2009-02-24 21:30:07 |
Evan Broder |
description |
Binary package hint: xen-utils-3.2
The xendomains init script has a couple of errors.
IMPACT: These errors cause the normal migrate then save then shutdown mechanisms to fail, and instead skip straight to the "shutdown all" stage. In addition to being a major departure from the expected behavior, this could cause loss of user data, if users expect the state of their VMs to be saved instead of destroyed.
PATCH: http://launchpadlibrarian.net/20457983/xen-3.2_3.2.0-0ubuntu11.debdiff for Hardy and http://launchpadlibrarian.net/20406413/xen-3.3_3.3.0-1ubuntu8.debdiff for Intrepid represent the minimal patch to restore functionality.
TEST CASE:
1. Start a Xen domU
2. Run /etc/init.d/xendomains stop
3. Observe that, after several errors are spewed, the domU is not saved to /var/lib/xen/save, as is the default Ubuntu config, but is instead shutdown.
REGRESSIONS: This is a two line patch whose implications can be pretty easily observed directly. It is highly unlikely to make things any less functional than they are now.
Please note, this is not the same as bug #208300. |
Binary package hint: xen-utils-3.2
The xendomains init script has a couple of errors.
IMPACT: These errors cause the normal migrate then save then shutdown mechanisms to fail, and instead skip straight to the "shutdown all" stage. In addition to being a major departure from the expected behavior, this could cause loss of user data, if users expect the state of their VMs to be saved instead of destroyed.
PATCH: http://launchpadlibrarian.net/20457983/xen-3.2_3.2.0-0ubuntu11.debdiff for Hardy and http://launchpadlibrarian.net/23083056/xen-3.3_3.3.0-1ubuntu7.1.debdiff for Intrepid represent the minimal patch to restore functionality.
TEST CASE:
1. Start a Xen domU
2. Run /etc/init.d/xendomains stop
3. Observe that, after several errors are spewed, the domU is not saved to /var/lib/xen/save, as is the default Ubuntu config, but is instead shutdown.
REGRESSIONS: This is a two line patch whose implications can be pretty easily observed directly. It is highly unlikely to make things any less functional than they are now.
Please note, this is not the same as bug #208300. |
|
2009-02-24 21:33:43 |
Evan Broder |
bug |
|
|
added attachment 'xen-3.3_3.3.0-1ubuntu7.1.debdiff' (xen-3.3_3.3.0-1ubuntu7.1.debdiff) |
2009-02-24 21:34:30 |
Evan Broder |
description |
Binary package hint: xen-utils-3.2
The xendomains init script has a couple of errors.
IMPACT: These errors cause the normal migrate then save then shutdown mechanisms to fail, and instead skip straight to the "shutdown all" stage. In addition to being a major departure from the expected behavior, this could cause loss of user data, if users expect the state of their VMs to be saved instead of destroyed.
PATCH: http://launchpadlibrarian.net/20457983/xen-3.2_3.2.0-0ubuntu11.debdiff for Hardy and http://launchpadlibrarian.net/23083056/xen-3.3_3.3.0-1ubuntu7.1.debdiff for Intrepid represent the minimal patch to restore functionality.
TEST CASE:
1. Start a Xen domU
2. Run /etc/init.d/xendomains stop
3. Observe that, after several errors are spewed, the domU is not saved to /var/lib/xen/save, as is the default Ubuntu config, but is instead shutdown.
REGRESSIONS: This is a two line patch whose implications can be pretty easily observed directly. It is highly unlikely to make things any less functional than they are now.
Please note, this is not the same as bug #208300. |
Binary package hint: xen-utils-3.2
The xendomains init script has a couple of errors.
IMPACT: These errors cause the normal migrate then save then shutdown mechanisms to fail, and instead skip straight to the "shutdown all" stage. In addition to being a major departure from the expected behavior, this could cause loss of user data, if users expect the state of their VMs to be saved instead of destroyed.
PATCH: http://launchpadlibrarian.net/20457983/xen-3.2_3.2.0-0ubuntu11.debdiff for Hardy and http://launchpadlibrarian.net/23083113/xen-3.3_3.3.0-1ubuntu7.1.debdiff for Intrepid represent the minimal patch to restore functionality.
TEST CASE:
1. Start a Xen domU
2. Run /etc/init.d/xendomains stop
3. Observe that, after several errors are spewed, the domU is not saved to /var/lib/xen/save, as is the default Ubuntu config, but is instead shutdown.
REGRESSIONS: This is a two line patch whose implications can be pretty easily observed directly. It is highly unlikely to make things any less functional than they are now.
Please note, this is not the same as bug #208300. |
|
2009-02-25 01:52:40 |
Bryce Harrington |
xen-3.3: status |
Confirmed |
Fix Committed |
|
2009-02-25 01:52:40 |
Bryce Harrington |
xen-3.3: statusexplanation |
Looks fine for an SRU. Bryce, mind sponsoring those, too? |
Thanks, upload sponsored. |
|
2009-02-25 02:07:02 |
Steve Langasek |
xen-3.3: status |
Fix Committed |
In Progress |
|
2009-02-25 02:07:02 |
Steve Langasek |
xen-3.3: statusexplanation |
Thanks, upload sponsored. |
|
|
2009-03-09 08:41:12 |
Launchpad Janitor |
xen-3.2: status |
Fix Committed |
Fix Released |
|
2009-03-09 10:01:01 |
Martin Pitt |
xen-3.3: status |
In Progress |
Fix Committed |
|
2009-04-17 14:10:48 |
Martin Pitt |
tags |
verification-needed |
verification-done |
|
2009-04-17 18:13:57 |
Evan Broder |
bug task added |
|
hardy-backports |
|
2009-04-20 10:23:30 |
Launchpad Janitor |
xen-3.3 (Ubuntu Intrepid): status |
Fix Committed |
Fix Released |
|
2009-04-20 17:11:02 |
Evan Broder |
summary |
errors in xendomains init script |
[hardy-backports] errors in xendomains init script |
|
2009-04-20 17:11:02 |
Evan Broder |
description |
Binary package hint: xen-utils-3.2
The xendomains init script has a couple of errors.
IMPACT: These errors cause the normal migrate then save then shutdown mechanisms to fail, and instead skip straight to the "shutdown all" stage. In addition to being a major departure from the expected behavior, this could cause loss of user data, if users expect the state of their VMs to be saved instead of destroyed.
PATCH: http://launchpadlibrarian.net/20457983/xen-3.2_3.2.0-0ubuntu11.debdiff for Hardy and http://launchpadlibrarian.net/23083113/xen-3.3_3.3.0-1ubuntu7.1.debdiff for Intrepid represent the minimal patch to restore functionality.
TEST CASE:
1. Start a Xen domU
2. Run /etc/init.d/xendomains stop
3. Observe that, after several errors are spewed, the domU is not saved to /var/lib/xen/save, as is the default Ubuntu config, but is instead shutdown.
REGRESSIONS: This is a two line patch whose implications can be pretty easily observed directly. It is highly unlikely to make things any less functional than they are now.
Please note, this is not the same as bug #208300. |
Binary package hint: xen-utils-3.2
The xendomains init script has a couple of errors.
These errors affected xen-3.3 3.3.0-1ubuntu7, which was backported to Hardy as 3.3.0-1ubuntu7~hardy1. Please backport xen-3.3 3.3.0-1ubuntu7.1 from Intrepid to Hardy to fix this problem for hardy-backports.
=====
IMPACT: These errors cause the normal migrate then save then shutdown mechanisms to fail, and instead skip straight to the "shutdown all" stage. In addition to being a major departure from the expected behavior, this could cause loss of user data, if users expect the state of their VMs to be saved instead of destroyed.
PATCH: http://launchpadlibrarian.net/20457983/xen-3.2_3.2.0-0ubuntu11.debdiff for Hardy and http://launchpadlibrarian.net/23083113/xen-3.3_3.3.0-1ubuntu7.1.debdiff for Intrepid represent the minimal patch to restore functionality.
TEST CASE:
1. Start a Xen domU
2. Run /etc/init.d/xendomains stop
3. Observe that, after several errors are spewed, the domU is not saved to /var/lib/xen/save, as is the default Ubuntu config, but is instead shutdown.
REGRESSIONS: This is a two line patch whose implications can be pretty easily observed directly. It is highly unlikely to make things any less functional than they are now.
Please note, this is not the same as bug #208300. |
|
2009-04-22 07:57:30 |
Martin Pitt |
bug |
|
|
added subscriber Ubuntu Backporters |
2009-04-22 07:57:47 |
Martin Pitt |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
2009-04-22 07:58:05 |
Martin Pitt |
removed subscriber Ubuntu Sponsors for main |
|
|
|
2009-05-21 20:40:13 |
agent 8131 |
tags |
verification-done |
server verification-done virtualization xen |
|
2009-07-18 19:45:19 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/hardy-updates/xen-3.2 |
|
2009-07-25 22:33:12 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic/xen-3.3 |
|
2009-07-25 22:39:07 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/intrepid-updates/xen-3.3 |
|
2009-11-11 04:39:14 |
John Dong |
hardy-backports: status |
New |
Confirmed |
|
2010-02-15 17:24:41 |
James Westby |
hardy-backports: status |
Confirmed |
Fix Released |
|
2010-02-15 17:24:51 |
James Westby |
hardy-backports: status |
Fix Released |
Fix Committed |
|
2010-03-10 00:39:39 |
Jonathan Riddell |
hardy-backports: status |
Fix Committed |
Fix Released |
|