Skip to contentSkip to conversation

New: VagrantFile provisioning step fails due to issue with grub-pc update

Buildroot bugzilla at busybox.net 1 participant 2 messages Jan 12, 2017 – Feb 26, 2017

lore
Share & tools
lore
#0 lore raw

https://bugs.busybox.net/show_bug.cgi?id=9581

Bug ID: 9581
Summary: VagrantFile provisioning step fails due to issue with
grub-pc update
Product: buildroot
Version: 2016.11
Hardware: All
OS: Mac OS
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: robiniddon at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---

Created attachment 6851
--> https://bugs.busybox.net/attachment.cgi?id=6851&action=edit
Patch to correct provisioning step in Vagrantfile

If you follow the steps in the manual to launch vagrant (download VagrantFile, run vagrant up) then the resulting VirtualBox VM hangs during the provisioning because the grub-pc update is asking a question but there is no interactive context in which the user can answer it.

The solution is to run the apt-get update with not only -y but also some magic options that make sure it really doesn't ask any questions.

The issue is described here:

http://askubuntu.com/questions/146921/how-do-i-apt-get-y-dist-upgrade-without-a-grub-config-prompt

I attach a patch that makes it so.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#1 lore raw

[Buildroot] [Bug 9581] VagrantFile provisioning step fails due to issue with grub-pc update

https://bugs.busybox.net/show_bug.cgi?id=9581

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #1 from Thomas Petazzoni <[email protected]> --- Fixed by
https://git.buildroot.org/buildroot/commit/?id=410082e1d980668385ffd2993920785e0fffd2c1.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.