Bug #16144
Document another workaround for a vagrant failure
100%
Description
When I try to build Tails, vagrant sometimes fails with
Initialization parameters must be an attributes hash, got NilClass nil (ArgumentError)
Restarting libvirtd
fixes this, as suggested here.
We should add this to our Known issues and workarounds section in contribute/build.
Subtasks
History
#1 Updated by segfault 2018-11-21 23:52:25
- Status changed from Confirmed to In Progress
Applied in changeset commit:tails|47d97641c49da1cde43a4d91cfcd2ccad6b89556.
#2 Updated by segfault 2018-11-21 23:53:18
- Assignee set to intrigeri
- QA Check set to Ready for QA
- Feature Branch set to bugfix/16144-document-workaround
#3 Updated by intrigeri 2018-11-22 07:53:34
- Assignee changed from intrigeri to segfault
There’s no reason why we should delay this improvement until the next release so I’ve transplanted your branch onto master
(git rebase --onto master origin/stable
).
I’ve added a couple small improvements on top, please review and merge into master once happy :)
#4 Updated by segfault 2018-11-22 15:24:31
re 1500fa0313b6fcb15601a8d2cd9a6f25b21d11f6:
I copied the hard-coded build command line from the section above:
To build an ISO image, execute the following command:
rake build && rake vm:halt
#5 Updated by segfault 2018-11-22 15:26:38
- Status changed from In Progress to Fix committed
- % Done changed from 0 to 100
Applied in changeset commit:tails|f0eb16be45328bbd21cf2af0c38e1174f095a3de.
#6 Updated by intrigeri 2018-11-22 15:58:32
> I copied the hard-coded build command line from the section above:
Sure. They have different purposes: that one is meant for 1st-timers while the workaround section can also be followed by people who build Tails everyday with a different command line.
#7 Updated by intrigeri 2018-11-22 16:05:36
- Status changed from Fix committed to Resolved
- Assignee deleted (
segfault) - QA Check changed from Ready for QA to Pass