The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/tast-tests/+/f6497f6c1bbd07245695211060096a7e5176d77e

commit f6497f6c1bbd07245695211060096a7e5176d77e
Author: Stephen Barber <smbarber@chromium.org>
Date: Thu Jul 26 13:29:09 2018

tast-tests: add vm.Webserver test

Add a test that ensures that a webserver installed in
the container is accessible from Chromium.

BUG= chromium:854923 
TEST=vm.Webserver

Change-Id: I76e50f435803697e42bc3af04034b67189ad49ed
Reviewed-on: https://chromium-review.googlesource.com/1132690
Commit-Ready: Stephen Barber <smbarber@chromium.org>
Tested-by: Stephen Barber <smbarber@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>

[add] https://crrev.com/f6497f6c1bbd07245695211060096a7e5176d77e/src/chromiumos/tast/local/bundles/cros/vm/webserver.go

Is this one fixed?

I want to update the test to include the port forwarding that we added.

Is 70 the right target milestone?

Marking this one as fixed. Jeff will be merging this into one big crostini test.

Opening the bug as test is failing in the lab due to "Failed to set up default container: failed to start VM: Failed to mount shared directory"

Stainless results: 
https://stainless.corp.google.com/search?view=matrix&row=board&col=build&first_date=2018-09-20&last_date=2018-10-03&test=tast.vm.Webserver%09&exclude_cts=true&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false

This test no longer fails on recent builds, marking as fixed again.