UTAH vm provisionings go on a loop on saucy hosts

Bug #1199349 reported by Para Siva
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
UTAH
Fix Released
High
Andy Doan

Bug Description

On saucy hosts with new utah installations (0.14ubuntu1-saucy1) the VM installations as part of run-utah-tests keep going on a loop and does not go into booting.

This happened when I installed
1. a fresh saucy host and then
2. Install libvirt and setup qemu-kvm
3. Installed latest utah on it and then when I run
4. sudo -u utah -i run_utah_tests.py -i /path/to/saucy-server-amd64.iso -p lp:ubuntu-test-cases/server/preseeds/mail-server.preseed lp:ubuntu-test-cases/server/runlists/mail-server.run -x /etc/utah/bridged-network-vm.xml

Not exactly sure if this is the cause, but I can only see the following on saucy hosts (failing ones) and not on raring where the issue can not be seen.
2013-07-09 12:17:19,193 cleanup WARNING: Exception while running cleanup function: Requested operation is not valid: domain is not running
2013-07-09 12:17:19,197 cleanup WARNING: OSError when changing directory permissions: [Errno 1] Operation not permitted: '/var/lib/utah/vm/utah-3-saucy-server-amd64/disk0.qcow2'
2013-07-09 12:17:19,374 cleanup WARNING: OSError when changing directory permissions: [Errno 1] Operation not permitted: '/tmp/utah-3-saucy-server-amd64_7A9aHm/initrd.gz'
2013-07-09 12:17:19,375 cleanup WARNING: OSError when changing directory permissions: [Errno 1] Operation not permitted: '/tmp/utah-3-saucy-server-amd64_7A9aHm/saucy-server-amd64.iso'
2013-07-09 12:17:19,375 cleanup WARNING: OSError when changing directory permissions: [Errno 1] Operation not permitted: '/tmp/utah-3-saucy-server-amd64_7A9aHm/kernel'
2013-07-09 12:17:19,397 cleanup WARNING: OSError when changing directory permissions: [Errno 1] Operation not permitted: '/tmp/utah-3-saucy-server-amd64_7A9aHm/initrd.gz'
2013-07-09 12:17:19,397 cleanup WARNING: OSError when changing directory permissions: [Errno 1] Operation not permitted: '/tmp/utah-3-saucy-server-amd64_7A9aHm/saucy-server-amd64.iso'
2013-07-09 12:17:19,397 cleanup WARNING: OSError when changing directory permissions: [Errno 1] Operation not permitted: '/tmp/utah-3-saucy-server-amd64_7A9aHm/kernel'

I'll attach the logs.

Revision history for this message
Para Siva (psivaa) wrote :
Revision history for this message
Para Siva (psivaa) wrote :
Revision history for this message
Para Siva (psivaa) wrote :
Revision history for this message
Para Siva (psivaa) wrote :
Para Siva (psivaa)
description: updated
Gema Gomez (gema)
Changed in utah:
importance: Undecided → High
Revision history for this message
Para Siva (psivaa) wrote :

This is not seen anynore, marking this incomplete

Changed in utah:
status: New → Incomplete
Revision history for this message
Para Siva (psivaa) wrote :

Reopening this because it is reproducible in a trusty host.

Changed in utah:
status: Incomplete → New
Revision history for this message
Andy Doan (doanac) wrote :

psivaa - I appended this line to my preseed and it seems to work. Can you try appending this to your preseed and let me know if solves your issue:

d-i debian-installer/exit/poweroff boolean true

Changed in utah:
assignee: nobody → Andy Doan (doanac)
Revision history for this message
Para Siva (psivaa) wrote :

That solved the issue. Running after editing /etc/utah/default-preseed.cfg to see if the upgrade jobs succeed as well.

Revision history for this message
Andy Doan (doanac) wrote :

That's great. We still have a bug somewhere I need to try and understand. Max added some context:

In utah/provisioning/vm.py, we do this:
xmlt.find('on_reboot').text = 'destroy'
That sets the on_reboot element of the KVM XML definition to destroy so a reboot will trigger a shutdown instead.

On line 452, after the VM is installed, we set it back to restart:
xml.find('on_reboot').text = 'restart'

Revision history for this message
Andy Doan (doanac) wrote :

I think I've released a fix for this:
  http://bazaar.launchpad.net/~utah/utah/dev/revision/1046

Changed in utah:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.