[hardy-backports] errors in xendomains init script
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Hardy Backports |
Fix Released
|
Undecided
|
Unassigned | ||
xen-3.2 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Hardy |
Fix Released
|
Undecided
|
Unassigned | ||
Intrepid |
Invalid
|
Undecided
|
Unassigned | ||
Jaunty |
Invalid
|
Undecided
|
Unassigned | ||
xen-3.3 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Hardy |
Invalid
|
Undecided
|
Unassigned | ||
Intrepid |
Fix Released
|
Undecided
|
Unassigned | ||
Jaunty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
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~
=====
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://
TEST CASE:
1. Start a Xen domU
2. Run /etc/init.
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.
Changed in xen-3.2: | |
status: | New → Confirmed |
description: | updated |
description: | updated |
description: | updated |
Changed in xen-3.3: | |
status: | Fix Committed → In Progress |
tags: |
added: verification-done removed: verification-needed |
tags: | added: server virtualization xen |
Changed in hardy-backports: | |
status: | New → Confirmed |
Changed in hardy-backports: | |
status: | Fix Committed → Fix Released |
The specific errors, emitted during startup, were one to do with cut, which was just a simple typo at line 186, in the parseln function, and the second was the test at line 196 caused an error saying (something like) "test: = unary operator expected. I simply wrapped that one in quotes (not sure if that was the right thing to do.)