Last modified: 2014-11-17 21:36:07 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T69571, the corresponding Phabricator task for complete and up-to-date bug report information.

Bug 67571 - Vagrant not starting properly on first boot (windows host)


Summary:	Vagrant not starting properly on first boot (windows host)

Status:	UNCONFIRMED

Product:	MediaWiki-Vagrant
Classification:	Unclassified
Component:	General (Other open bugs)
Version:	unspecified
Hardware:	All All

Importance:	Unprioritized normal
Target Milestone:	---
Assigned To:	Nobody - You can work on this!

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-07-06 21:39 UTC by Yuri Astrakhan
Modified:	2014-11-17 21:36 UTC (History)
CC List:	3 users (show)

See Also:
Web browser:	---
Mobile Platform:	---
Assignee Huggle Beta Tester:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Yuri Astrakhan 2014-07-06 21:39:03 UTC

On Windows 8.1 x64, when a new VM is created, it almost always does not start from the first time (I get lots of "default: Warning: Remote connection disconnect. Retrying..." followed by an error). Repeating it with "vagrant up" states that the machine is up. I have to "vagrant halt -f" and "vagrant up", sometimes several times, until initial provisioning starts up. I saw this behavior in 1.5.x and now in the latest 1.6.3 version.

Comment 1 Bryan Davis 2014-08-20 00:36:43 UTC

This sounds like a Vagrant and/or Virtualbox issue rather than an MediaWiki-Vagrant issue. Is there anything actionable for the MWV maintainer team here?

Comment 2 Bryan Davis 2014-11-17 21:36:07 UTC

Bulk unassigning bugs from Ori.

Wikimedia Bugzilla is closed!

Search

Personal tools

Navigation

Links