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

Example in Getting Started is not working. #38

Closed
deorbit opened this issue Jun 11, 2019 · 1 comment
Closed

Example in Getting Started is not working. #38

deorbit opened this issue Jun 11, 2019 · 1 comment

Comments

@deorbit
Copy link

@deorbit deorbit commented Jun 11, 2019

Following the steps at https://sqoop.solo.io/getting_started/ on a fresh minikube cluster, the query

{
  pets {
    id
  }
}

gives the following error

 "errors": [
    {
      "message": "executing resolver for field \"pets\": failed executing resolver for Query.pets: performing http post: Post http://127.0.0.1:9090/gloo-system.petstore.Query.pets: dial tcp 127.0.0.1:9090: connect: connection refused"
    }
  ]
}

Envoy logs (kubectl logs -n gloo-system sqoop-cdf94f envoy) reveal the following error repeated many times per second:

[2019-06-11 17:43:51.726][6][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_mux_subscription_lib/common/config/grpc_mux_subscription_impl.h:70] gRPC config for type.googleapis.com/envoy.api.v2.Listener rejected: Error adding/updating listener sqoop-listener: Unable to parse JSON as proto (INVALID_ARGUMENT:normalize_path: Cannot find field.): {"upgrade_configs":[{"upgrade_type":"websocket"}],"http_filters":[{"name":"envoy.fault"},{"name":"envoy.cors"},{"name":"io.solo.transformation"},{"name":"envoy.router"}],"normalize_path":true,"rds":{"config_source":{"ads":{}},"route_config_name":"sqoop-listener-routes"},"stat_prefix":"http"}
sqoopctl --version
sqoopctl version 0.2.6

minikube version
minikube version: v1.1.0
@ilackarms
Copy link
Member

@ilackarms ilackarms commented Jun 12, 2019

thanks for reporting this issue! it's a real bug. i tested it locally and discovered the problem:

we recently updated the version of Gloo (envoy config server) that sqoop is using without updating the version of Envoy itself.

the quick fix for this is to update the sqoop deployment. the image for the envoy container should be quay.io/solo-io/gloo-envoy-wrapper:0.13.25.

you can quickly update this with the command

kubectl set image -n gloo-system deployment/sqoop envoy=quay.io/solo-io/gloo-envoy-wrapper:0.13.25

however we will definitely need to update our helm chart with the fix. thanks for reporting!

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

2 participants