[Bug 703959] Re: execscript is run too early
** Changed in: vm-builder (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/703959 Title: execscript is run too early To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/703959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 703959] Re: execscript is run too early
[Expired for vm-builder (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vm-builder (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/703959 Title: execscript is run too early To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/703959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 703959] Re: execscript is run too early
** Changed in: vm-builder (Ubuntu) Assignee: Soren Hansen (soren) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/703959 Title: execscript is run too early -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 703959] Re: execscript is run too early
Indeed, looking at the lucid source, I see that the post_install() calls the execscripts before the --only-chroot checks, whereas hypervisor.py:install_os(), which installs the bootloader, gets called after. I assume it's there for a reason so don't want to blindly move it. Would like guidance from Soren: was the intent of execscripts to be called after full os install, or after initial chroot build? Should a new --os-execripts or somesuch option be added to allow scripts to be called after full OS install? As a workaround you should be able to have the early execscript create an /etc/default/grub, though I'm not sure whether dpkg would then require interaction to ask whether to use your existing /etc/default/grub. ** Changed in: vm-builder (Ubuntu) Assignee: (unassigned) => Soren Hansen (soren) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/703959 Title: execscript is run too early -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 703959] Re: execscript is run too early
** Attachment added: "debug output" https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/703959/+attachment/1796963/+files/typescript.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/703959 Title: execscript is run too early -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 703959] Re: execscript is run too early
** Attachment added: "--execscript" https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/703959/+attachment/1796962/+files/exec.sh.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/703959 Title: execscript is run too early -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 703959] Re: execscript is run too early
Command line: sudo vmbuilder kvm ubuntu --config /tmp/703959/vm.cfg --ip 10.0.0.1 --hostname bug703959 --dest=/tmp/703959/vm --debug -o ** Attachment added: "vmbuilder config file" https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/703959/+attachment/1796961/+files/vm.cfg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/703959 Title: execscript is run too early -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 703959] Re: execscript is run too early
1. Yes. 2. I will attach config files and debug output. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/703959 Title: execscript is run too early -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 703959] Re: execscript is run too early
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: 1. Is this reproducible? 2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible. This will help us to find and resolve the problem. ** Changed in: vm-builder (Ubuntu) Importance: Undecided => Low ** Changed in: vm-builder (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/703959 Title: execscript is run too early -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs