[Bug 216761] Re: errors in xendomains init script

[Evan Broder]

Ok - one last fix remains, and then we're done with this bug.

xen-3.3 3.3.0-1ubuntu7~hardy1 is currently in hardy-backports.
Backporting 3.3.0-1ubuntu7.1 from Intrepid to Hardy should be safe and
should fix the bug in backports.

** Summary changed:

- errors in xendomains init script
+ [hardy-backports] errors in xendomains init script

** Description changed:

  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.

-- 
[hardy-backports] errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Backports Testing Team, which is subscribed to Hardy Backports.