https://bugzilla.wikimedia.org/show_bug.cgi?id=67976
--- Comment #8 from Tisza Gergő ---
Not sure if this is really related to the change you mention. The most recent
box I am experiencing this on is at I91d51f6deb0b12b795f705cf8895783a11fa8695.
Looks like all the old boxes became unusable when I
https://bugzilla.wikimedia.org/show_bug.cgi?id=67976
--- Comment #9 from Tisza Gergő ---
The error message after running vagrant reload is slightly different though:
$ vagrant reload
[default] Attempting graceful shutdown of VM...
[default] Clearing any previously set forwarded ports...
[default
https://bugzilla.wikimedia.org/show_bug.cgi?id=67976
--- Comment #10 from Bryan Davis ---
(In reply to Tisza Gergő from comment #9)
> The error message after running vagrant reload is slightly different though:
>
> $ vagrant reload
[...snip...]
> [default] Machine booted and ready!
> GuestAdditi
https://bugzilla.wikimedia.org/show_bug.cgi?id=67976
--- Comment #11 from Gerrit Notification Bot ---
Change 147878 merged by jenkins-bot:
Defer deleting legacy cache directories
https://gerrit.wikimedia.org/r/147878
--
You are receiving this mail because:
You are on the CC list for the bug.
_
https://bugzilla.wikimedia.org/show_bug.cgi?id=67976
Bryan Davis changed:
What|Removed |Added
Status|PATCH_TO_REVIEW |RESOLVED
Resolution|---
https://bugzilla.wikimedia.org/show_bug.cgi?id=67976
--- Comment #13 from Tisza Gergő ---
(In reply to Bryan Davis from comment #12)
> The fix was to make the old git cache happy by `mkdir -p apt-cache/partial`
> and then `vagrant up`.
This does not work for me, presumably because folder sharing
https://bugzilla.wikimedia.org/show_bug.cgi?id=67976
Bryan Davis changed:
What|Removed |Added
CC||bda...@wikimedia.org
--- Comment #1 from
https://bugzilla.wikimedia.org/show_bug.cgi?id=67976
--- Comment #2 from Tisza Gergő ---
Yes, this doesn't happen in a new vagrant installation, but breaks an upgrade
attempt of an old one in a really ugly way (in the end I had to migrate
everything manually to a new box).
--
You are receiving
https://bugzilla.wikimedia.org/show_bug.cgi?id=67976
--- Comment #3 from Bryan Davis ---
Looking at this closer, the problem is caused by cleaning up the previous
apt-cache/** directories before puppet runs on the VM.
We install a file at /etc/apt/apt.conf.d/20shared-cache to configure an
altern
https://bugzilla.wikimedia.org/show_bug.cgi?id=67976
--- Comment #4 from Gerrit Notification Bot ---
Change 147878 had a related patch set uploaded by BryanDavis:
Defer deleting legacy cache directories
https://gerrit.wikimedia.org/r/147878
--
You are receiving this mail because:
You are on th
https://bugzilla.wikimedia.org/show_bug.cgi?id=67976
Gerrit Notification Bot changed:
What|Removed |Added
Status|NEW |PATCH_TO_REVIEW
--
You are
https://bugzilla.wikimedia.org/show_bug.cgi?id=67976
--- Comment #5 from Tisza Gergő ---
After applying the patch, running vagrant reload fails with the same message.
However, virtualbox-guest-dkms is now installed on the VM, and the mount fails
with a different error message:
/sbin/mount.vboxsf
https://bugzilla.wikimedia.org/show_bug.cgi?id=67976
--- Comment #6 from Tisza Gergő ---
Ignore me. I got lost while context switching and ran the commands on the host.
The error is still the same as described in comment 0.
This might be only because this box is already in a messed-up state; I c
https://bugzilla.wikimedia.org/show_bug.cgi?id=67976
--- Comment #7 from Bryan Davis ---
(In reply to Tisza Gergő from comment #6)
> This might be only because this box is already in a messed-up state; I can
> try upgrading another box if you think it will work now.
If you have the energy to try
14 matches
Mail list logo
