Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

x/build: vcs-test.golang.org is down #27127

Closed
andybons opened this issue Aug 21, 2018 · 7 comments
Closed

x/build: vcs-test.golang.org is down #27127

andybons opened this issue Aug 21, 2018 · 7 comments
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done. Soon This needs to be done soon. (regressions, serious bugs, outages)
Milestone
Unreleased

Comments

@andybons
Copy link
Member

We are aware of the issue and are working on it.
@andybons andybons added NeedsFix The path to resolution is known, but the work has not been done. Soon This needs to be done soon. (regressions, serious bugs, outages) labels Aug 21, 2018
@gopherbot gopherbot added this to the Unreleased milestone Aug 21, 2018
@gopherbot gopherbot added the Builders x/build issues (builders, bots, dashboards) label Aug 21, 2018
@gopherbot
Copy link

Change https://golang.org/cl/130418 mentions this issue: vcs-test: enable ACME ALPN challenge and use autocert RSA fallback

@gopherbot
Copy link

Change https://golang.org/cl/130475 mentions this issue: vcs-test: fix deployment and systemd socket association

gopherbot pushed a commit to golang/build that referenced this issue Aug 21, 2018
@FiloSottile
vcs-test/vcweb: enable ACME ALPN challenge and use autocert RSA fallback
0cb088d 
The SNI challenge is not supported by Let's Encrypt anymore, replaced by
the ALPN one, which requires an extra config entry.

Also, autocert now knows how to do RSA fallback, so remove that code.

Updates golang/go#27127

Change-Id: I45f907101a7c7a57d1a8376208dba4afb10ed6fd
Reviewed-on: https://go-review.googlesource.com/130418
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
gopherbot pushed a commit to golang/build that referenced this issue Aug 21, 2018
@FiloSottile
vcs-test: fix deployment and systemd socket association
92cee07 
Quoting https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances
under "Best Practices":

> Grant the instance the https://www.googleapis.com/auth/cloud-platform
> scope to allow full access to all Google Cloud APIs, so that the IAM
> permissions of the instance are completely determined by the IAM roles
> of the service account.

Updates golang/go#27127

Change-Id: Icceb3b17a12223199efd67d27f6bca2b71f8fadc
Reviewed-on: https://go-review.googlesource.com/130475
Reviewed-by: Andrew Bonventre <andybons@golang.org>
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
@FiloSottile FiloSottile mentioned this issue Aug 21, 2018
Closed
@andybons andybons mentioned this issue Aug 21, 2018
Closed
@jasonkeene
Copy link
Contributor

I am trying to run some git module tests right now and it appears to be down for me.

2018/08/30 20:05:52 git clone --mirror https://vcs-test.golang.org/git/gitrepo1 /var/folders/f2/8qjhqmss5ssb6ccx15bxvvl80000gn/T/gitrepo-test-403044532/gitrepo2 in : exit status 128:
        Cloning into bare repository '/var/folders/f2/8qjhqmss5ssb6ccx15bxvvl80000gn/T/gitrepo-test-403044532/gitrepo2'...
        fatal: unable to access 'https://vcs-test.golang.org/git/gitrepo1/': Failed to connect to vcs-test.golang.org port 443: Operation timed out
FAIL    cmd/go/internal/modfetch/codehost       75.182s

@andybons
Copy link
Member Author

We are aware of the issue still and apologize. There are some unforeseen internal issues that are still being worked out.

@jasonkeene
Copy link
Contributor

@andybons Thanks for the update.

I don't have a lot of context on why these tests use vcs-test.golang.org. Do we need to have these tests talk to a vcs server on the internet or can the tests just start this server themselves? If the server can be ran locally I would think that would be better than having them rely on the availability of vcs-test.golang.org.

@FiloSottile
Copy link
Contributor

vcs-test.golang.org is back up.

@andybons
Copy link
Member Author

andybons commented Sep 2, 2018

@jasonkeene I don’t know the history of vcs-test, so I’m unable to answer your question. Perhaps file a new issue specific to your question?

@jasonkeene jasonkeene mentioned this issue Sep 4, 2018
Closed
@golang golang locked and limited conversation to collaborators Sep 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done. Soon This needs to be done soon. (regressions, serious bugs, outages)
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
4 participants
@jasonkeene @andybons @FiloSottile @gopherbot