[Bug 1004158] Re: ltsp-update-image doesn't work on precise in an openvz container

[Launchpad Bug Tracker]

This bug was fixed in the package ltsp - 5.3.7-0ubuntu2.1

---------------
ltsp (5.3.7-0ubuntu2.1) precise-proposed; urgency=low

  * Cherry-pick upstream bugfixes:
    - Fix ionice on OpenVZ (r2242) (LP: #1004158)
    - Fix variable name conflict for ltsp-cluster (r2303) (LP: #1008618)
    - Check X_COLOR_DEPTH before overwritting with 16bit (r2316) (LP: #1010198)
 -- Stephane Graber <stgraber at ubuntu.com>   Fri, 08 Jun 2012 10:55:10 -0400

** Changed in: ltsp (Ubuntu Precise)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ltsp in Ubuntu.
https://bugs.launchpad.net/bugs/1004158

Title:
  ltsp-update-image doesn't work on precise in an openvz container

Status in Linux Terminal Server Project:
  Fix Released
Status in “ltsp” package in Ubuntu:
  Triaged
Status in “ltsp” source package in Precise:
  Fix Released
Status in “ltsp” source package in Quantal:
  Triaged

Bug description:
  [impact]
  when generating the image, if we do it inside an openvz container, the ionice command make the the process fail.

  [test case]
  in a openvz container run:
  root at ltsp-root03:~# ltsp-update-image -n -a i386
  Regenerating kernel...
  Skipping yaboot configuration. install yaboot package if you need it.
  Skipping netabootwrap images. Install the aboot package if you need them.
  Skipping sparc piggyback images. Install the sparc-utils package if you need them.
  Done.
  Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/i386
  ionice: ioprio_set failed: Operation not permitted
  Error: mksquashfs failed to build the ltsp image, exiting

  [regression potential]
  really low, the change consist of testing if ionice works on a command to set it.
  if it fails, ionice is unset.

  [development fix]
  I know this section is deprecated but it's actually relevant in this case ;)
  The fix hasn't hit quantal yet because of some massive packaging rework going on with LTSP to try and bring us in sync with Debian. I can guarantee that we will have a new upstream release in quantal that will include this fix. ETA is of a couple of weeks.

  we should pull this commit to fix the issue in precise and quantal
  http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2242

To manage notifications about this bug go to:
https://bugs.launchpad.net/ltsp/+bug/1004158/+subscriptions