Closed Bug 1492911 Opened 6 years ago Closed 5 years ago

Vagrant provision fails once every two attempts after Mojolicious migration

Categories

(bugzilla.mozilla.org :: Developer Box, defect)

Product:
bugzilla.mozilla.org
Component:
Developer Box
Version:
Development
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: kohei, Assigned: dylan)

References

(Regression)

Details

(Keywords: regression) 

https://github.com/mozilla-bteam/bmo/blob/master/README.rst#making-changes-and-seeing-them

If you run `vagrant rsync && vagrant provision --provision-with update`, the server will be down. You have to always run `vagrant rsync && vagrant provision` to see the changes on Mojo.
Flags: needinfo?(dylan)
Sometimes even a full provision will kill the server.
Summary: Vagrant partial provision no longer works after Mojolicious migration → Vagrant provision fails once every two attempts after Mojolicious migration
It’s happening not randomly but once every two provisions, as far as I test locally. So if the command fails, you can just run it again to restart the server.
15:37 <dylanwh> anyone have a good example of a sysv-init script for hypnotoad?
15:38 <dylanwh> I wrote one but it seems to fail restarts sometimes
15:40 <mst> dylanwh: let Daemon::Control generate it for you?

https://metacpan.org/pod/Daemon::Control
Assignee: nobody → dylan
Flags: needinfo?(dylan)
I thought dylan said on IRC he found the culprit.
Flags: needinfo?(kohei.yoshino)
Flags: needinfo?(kohei.yoshino) → needinfo?(dylan)

start_morbo made this problem moot.

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(dylan)
Resolution: --- → INCOMPLETE
No longer blocks: bmo-mojo
Regressed by: bmo-mojo
You need to log in before you can comment on or make changes to this bug.