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

Bug #1004158 reported by Marc Gariépy on 2012-05-24
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LTSP5
Undecided
Unassigned
ltsp (Ubuntu)
Low
Stéphane Graber
Precise
Low
Stéphane Graber
Quantal
Low
Stéphane Graber

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@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

Marc Gariépy (mgariepy) on 2012-05-24
Changed in ltsp (Ubuntu):
milestone: none → precise-updates
Marc Gariépy (mgariepy) on 2012-05-24
Changed in ltsp (Ubuntu):
milestone: precise-updates → quantal-alpha-1
milestone: quantal-alpha-1 → precise-updates
milestone: precise-updates → none
Stéphane Graber (stgraber) wrote :

As discussed on IRC, won't SRU only for that as OpenVZ isn't a supported container technology in 12.04 but it'll be bundled whenever we SRU ltsp for Precise.

As it's commited upstream, it'll also land with the next LTSP uploaded in Quantal.

Changed in ltsp:
status: New → Fix Committed
Changed in ltsp (Ubuntu Precise):
status: New → Triaged
Changed in ltsp (Ubuntu Quantal):
status: New → Triaged
importance: Undecided → Low
Changed in ltsp (Ubuntu Precise):
importance: Undecided → Low
milestone: none → precise-updates
assignee: nobody → Stéphane Graber (stgraber)
Changed in ltsp (Ubuntu Quantal):
assignee: nobody → Stéphane Graber (stgraber)
Alkis Georgopoulos (alkisg) wrote :

Fix released in LTSP 5.4.0.

Changed in ltsp:
status: Fix Committed → Fix Released
Marc Gariépy (mgariepy) on 2012-06-08
description: updated
Changed in ltsp (Ubuntu Precise):
status: Triaged → In Progress
description: updated

Hello Marc, or anyone else affected,

Accepted ltsp into precise-proposed. The package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in ltsp (Ubuntu Precise):
status: In Progress → Fix Committed
tags: added: verification-needed
Marc Gariépy (mgariepy) wrote :

just tested the package from proposed, it work like it should.

Thanks for the upload.

tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Fri, 08 Jun 2012 10:55:10 -0400

Changed in ltsp (Ubuntu Precise):
status: Fix Committed → Fix Released
Changed in ltsp (Ubuntu Quantal):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers