Re: [tor-bugs] #21838 [Applications/Tor Browser]: Gitian VM creation fails on Ubuntu 16.x machines in the unmount step

[Tor Bug Tracker & Wiki]

#21838: Gitian VM creation fails on Ubuntu 16.x machines in the unmount step
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-gitian|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by dcf):

 * cc: dcf (added)


Comment:

 Replying to [comment:2 boklm]:
 > I am able to reproduce this error in an Ubuntu 16.10 VM. It seems to be
 caused by `/usr/sbin/update-grub` returning a error when run inside the
 wheezy chroot, and then the cleanup after this error not unmounting things
 in the right order.

 Here's a previous tbb-dev discussion that mentions this problem and has a
 [http://lists.torproject.org/pipermail/tbb-
 dev/attachments/20160410/8640e727/attachment.patch hack-around patch]:
   https://lists.torproject.org/pipermail/tbb-dev/2016-April/000358.html
   I ran into two problems that I tried to fix by patching vmbuilder. The
 first is that the call to `update-grub -y` would fail. I traced the
 problem to a lack of /dev inside the chroot; `update-grub` runs
   {{{
 grub-probe --device-map=/boot/grub/device.map -t device /
   }}}
   which fails with
   {{{
 grub-probe: error: cannot find a device for / (is /dev mounted?).
   }}}
   For this, I copy-pasted some code to bind-mount /dev before the call and
 unmount it after.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21838 [Applications/Tor Browser]: Gitian VM creation fails on Ubuntu 16.x machines in the unmount step

[Tor Bug Tracker & Wiki]

#21838: Gitian VM creation fails on Ubuntu 16.x machines in the unmount step
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-gitian|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by arlolra):

 Replying to [comment:1 boklm]:
 > As a temporary workaround, I uploaded VM images that you can be copied
 to the `gitian-builder` directory:

 Don't I need the ssh keys as well?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21838 [Applications/Tor Browser]: Gitian VM creation fails on Ubuntu 16.x machines in the unmount step

[Tor Bug Tracker & Wiki]

#21838: Gitian VM creation fails on Ubuntu 16.x machines in the unmount step
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-gitian|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by boklm):

 I am able to reproduce this error in an Ubuntu 16.10 VM. It seems to be
 caused by `/usr/sbin/update-grub` returning a error when run inside the
 wheezy chroot, and then the cleanup after this error not unmounting things
 in the right order.

 I have not been able to find why update-grub is failing when we are using
 Ubuntu 16.10. The logs only say this:
 {{{
 2017-05-05 13:51:00,774 DEBUG   : ['chroot', '/tmp/tmpdGQM2s', '/usr/sbin
 /update-grub', '-y']
 2017-05-05 13:51:00,779 INFO: Searching for GRUB installation
 directory ... found: /boot/grub
 2017-05-05 13:51:00,886 INFO: Probing devices to guess BIOS drives.
 This may take a long time.
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21838 [Applications/Tor Browser]: Gitian VM creation fails on Ubuntu 16.x machines in the unmount step

[Tor Bug Tracker & Wiki]

#21838: Gitian VM creation fails on Ubuntu 16.x machines in the unmount step
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-gitian|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by boklm):

 As a temporary workaround, I uploaded VM images that you can be copied to
 the `gitian-builder` directory:
 https://people.torproject.org/~boklm/tmp/bug_21838/
 https://people.torproject.org/~boklm/tmp/bug_21838/sha256sums.txt
 https://people.torproject.org/~boklm/tmp/bug_21838/sha256sums.txt.asc

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #21838 [Applications/Tor Browser]: Gitian VM creation fails on Ubuntu 16.x machines in the unmount step

[Tor Bug Tracker & Wiki]

#21838: Gitian VM creation fails on Ubuntu 16.x machines in the unmount step
--+
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-gitian
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 There have been reports that creating Gitian VMs on Ubuntu 16.x machines
 fails with error messages like:
 {{{
 2016-10-06 15:11:05,650 INFO: umount: /tmp/tmpxmUBiv/: target is busy
 2016-10-06 15:11:05,651 INFO: (In some cases useful info about
 processes that
 2016-10-06 15:11:05,651 INFO:  use the device is found by
 lsof(8) or fuser(1).)
 2016-10-06 15:11:05,651 ERROR   : Process (['umount', '/tmp/tmpxmUBiv/'])
 returned 32. stdout: , stderr: umount: /tmp/tmpxmUBiv/: target is busy
 (In some cases useful info about processes that
  use the device is found by lsof(8) or fuser(1).)

 Traceback (most recent call last):
   File "/usr/local/bin/vmbuilder", line 24, in 
 cli.main()
   File "/usr/local/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py",
 line 228, in main
 hypervisor.install_os()
   File "/usr/local/lib/python2.7/dist-packages/VMBuilder/hypervisor.py",
 line 70, in install_os
 self.call_hooks('install_bootloader', self.chroot_dir, self.disks)
   File "/usr/local/lib/python2.7/dist-packages/VMBuilder/distro.py", line
 69, in call_hooks
 self.cleanup()
   File "/usr/local/lib/python2.7/dist-packages/VMBuilder/distro.py", line
 44, in cleanup
 self._cleanup_cbs.pop(0)()
   File "/usr/local/lib/python2.7/dist-packages/VMBuilder/disk.py", line
 409, in umount
 run_cmd('umount', self.mntpath)
   File "/usr/local/lib/python2.7/dist-packages/VMBuilder/util.py", line
 120, in run_cmd
 raise VMBuilderException, "Process (%s) returned %d. stdout: %s,
 stderr: %s" % (args.__repr__(), status, mystdout.buf, mystderr.buf)
 VMBuilder.exception.VMBuilderException: Process (['umount',
 '/tmp/tmpxmUBiv/']) returned 32. stdout: , stderr: umount:
 /tmp/tmpxmUBiv/: target is busy
 (In some cases useful info about processes that
  use the device is found by lsof(8) or fuser(1).)

 qemu-img: target-wheezy-i386.qcow2: Could not open 'base-
 wheezy-i386.qcow2': No such file or directory
 i386 wheezy VM creation failed
 }}}

 And, indeed, for some reason there seem to be still resources used:
 {{{
 /dev/dm-12 on /tmp/tmp9k2g2E type ext3 (rw,relatime,data=ordered)
 /dev/sda1 on /tmp/tmp9k2g2E/tmp/vmbuilder-grub/tmpUE0GzK type ext4
 (rw,relatime,errors=remount-ro,data=ordered)
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs