Closed Bug 892271 Opened 13 years ago Closed 12 years ago

socorro-vagrant jenkins job failing since vagrant upgrade

Categories

(Infrastructure & Operations Graveyard :: WebOps: Socorro, task, P5)

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Socorro
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rhelmer, Assigned: bburton)

Details

Since vagrant was recently upgraded (sometime around July 8th), every socorro-vagrant job is starting off OK but then the virtualbox shared folder is going read-only after a short period of time. We saw something similar in the distant past where the problem was a too-old virtualbox version for vagrant, probably worth updating virtualbox on there before we dig deeper. I am using VirtualBox 4.2.12 and Vagrant 1.2.1 together locally on Mac and a complete run is working (for what it's worth)
I've disabled IRC notification for the socorro-vagrant job until it's working consistently again.
I upgraded to VirtualBox 4.2 [root@jenkins1.dmz.phx1 ~]# rpm -qa | grep VirtualBox VirtualBox-4.2-4.2.16_86992_el6-1.x86_64 [root@jenkins1.dmz.phx1 ~]# /etc/init.d/vboxdrv start Starting VirtualBox kernel modules [ OK ] Try the build now
Assignee: server-ops-webops → bburton
Status: NEW → ASSIGNED
Priority: -- → P5
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.