Repository navigation
Local Cocoon servers fail with "Failed host lookup: 'metadata.google.internal'" #129651
Description
The flutter-dashboard project is locked down, and seems to be missing read access to the flutter team. These ACLs are needed for developers to run the servers locally.
Local verification
cd cocoon/auto_submit
export GOOGLE_CLOUD_PROJECT=flutter-dashboard
dart bin/server.dart # FailsCurrent failure
$ dart bin/server.dart
Unhandled exception:
Failed host lookup: 'metadata.google.internal'
#0 IOClient.send (package:http/src/io_client.dart:94:7)
<asynchronous suspension>
#1 BaseClient._sendUnstreamed (package:http/src/base_client.dart:93:32)
<asynchronous suspension>
#2 MetadataServerAuthorizationFlow._getScopes (package:googleapis_auth/src/oauth2_flows/metadata_server.dart:89:22)
<asynchronous suspension>
#3 Future.wait.<anonymous closure> (dart:async/future.dart:525:21)
<asynchronous suspension>
#4 MetadataServerAuthorizationFlow.run (package:googleapis_auth/src/oauth2_flows/metadata_server.dart:63:21)
<asynchronous suspension>
#5 clientFromFlow (package:googleapis_auth/src/oauth2_flows/base_flow.dart:27:25)
<asynchronous suspension>
#6 clientViaMetadataServer (package:googleapis_auth/src/metadata_server_client.dart:43:5)
<asynchronous suspension>
#7 clientViaApplicationDefaultCredentials (package:googleapis_auth/auth_io.dart:95:10)
<asynchronous suspension>
#8 _obtainStorageService (package:appengine/src/appengine_internal.dart:237:22)
<asynchronous suspension>
#9 _initializeAppEngine (package:appengine/src/appengine_internal.dart:175:26)
<asynchronous suspension>
#10 _withAppEngineServicesInternal.<anonymous closure> (package:appengine/src/appengine_internal.dart:102:45)
<asynchronous suspension>
#11 main (file:///Users/chillers/cocoon/auto_submit/bin/server.dart:22:3)
<asynchronous suspension>
Activity
CaseyHillers commentedon Jun 27, 2023
@drewroengoogle do you know how I can map
metadata.google.internalto an existing ACL? I haven't ran Cocoon servers locally since ~January 2022, which seems to align with the GCP ACL changes.\cc @Hixie for developing the triage bot
drewroengoogle commentedon Jun 27, 2023
Off the top of my head, I'm not sure. I will take a look either this afternoon or tomorrow and see if I can find the permissions that are needed to get this working!
drewroengoogle commentedon Jun 28, 2023
@CaseyHillers Did you run into this while you were already logged in via
gcloud auth login? I can reproduce this, but only if I don't have.config/gcloud/application_default_credentials.jsonset. Otherwise, the client is created via my credentials as shown here.CaseyHillers commentedon Jul 5, 2023
Thanks! That worked for me.
It would help to have package:gcloud check for authentication, then throw a more help exception.
I'm running into other issues where most of https://cloud.google.com/appengine/docs/standard/nodejs/runtime#environment_variables needs to be defined before I can run a local instance.
drewroengoogle commentedon Jul 18, 2023
Sorry, I meant to follow up on this earlier. I know we have an internal link (go/flutter-cocoon-internal) that specifies some of the variables that need to be set. Are there additional ones beyond what is documented there that are being required?
CaseyHillers commentedon Aug 15, 2023
I'm seeing this in a brand new service. As my work around, I've created
bin/local_server.dartwhich skips the AppEngine zoneyusuf-goog commentedon Sep 7, 2023
Anything still needs to be done here?
CaseyHillers commentedon Sep 7, 2023
Splitting bin/server.dart into a smaller script, bin/local_server.dart that skips the appengine zone will fix this.
flutter-triage-bot commentedon Sep 20, 2023
This issue is missing a priority label. Please set a priority label when adding the
triaged-infralabel.flutter-triage-bot commentedon Sep 22, 2023
This issue is missing a priority label. Please set a priority label when adding the
triaged-infralabel.[app_dart] Refactor server to run locally (#3364)
github-actions commentedon Jan 17, 2024
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.