hashicorp / consul

Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.
https://www.consul.io
Other
28.31k stars 4.42k forks source link

Consul UI error after upgrade to 1.11.3. #12835

Open Peter2121 opened 2 years ago

Peter2121 commented 2 years ago

Overview of the Issue

List of service instances in UI is not shown correctly in Consul v1.11.3. Error 500 is present in browser with the following text returned by Consul: Connect must be enabled in order to use this endpoint

The URL of this request is: http://10.192.20.117:8500/v1/discovery-chain/myservice?dc=mydc

The URL of the main page is: http://10.192.20.117:8500/ui/mydc/services/myservice/instances

The UI was worked correctly before upgrade from v1.10.3. Consul is installed from OS package, this is the last version present in ports/packages.

It seems to be a regression as I found the same problem seen before: https://github.com/hashicorp/consul/issues/6890

Reproduction Steps

Connect to a working node of cluster after upgrade, go to 'Services', click on service name.

Consul info for both Client and Server

Client info ``` Firefox 95.0.2 (64-bit) on FreeBSD 12.2 x64. The same error is present on any web browser. ```
Server info ``` # consul info agent: check_monitors = 0 check_ttls = 0 checks = 0 services = 0 build: prerelease = revision = e319d7ed version = 1.11.3 consul: acl = enabled bootstrap = false known_datacenters = 1 leader = false leader_addr = 10.192.20.117:8300 server = true raft: applied_index = 10155825 commit_index = 10155825 fsm_pending = 0 last_contact = 50.802028ms last_log_index = 10155825 last_log_term = 406410 last_snapshot_index = 10144497 last_snapshot_term = 406410 latest_configuration = [{Suffrage:Voter ID:c591218e-0950-8ec4-93e1-fb977a5c2ec2 Address:10.192.20.116:8300} {Suffrage:Voter ID:e957bd74-cee8-2560-b176-bef281c4e2 e8 Address:10.192.20.117:8300} {Suffrage:Voter ID:1804570e-b6db-bfaf-921e-5cc5f3df1999 Address:10.192.20.115:8300} {Suffrage:Voter ID:bde0ce24-fbbf-0a5e-1c22-dc86ba4f1fa 3 Address:10.192.7.130:8300} {Suffrage:Voter ID:4134655e-7ea0-7971-8b64-05b7e2879620 Address:10.192.6.135:8300}] latest_configuration_index = 0 num_peers = 4 protocol_version = 3 protocol_version_max = 3 protocol_version_min = 0 snapshot_version_max = 1 snapshot_version_min = 0 state = Follower term = 406410 runtime: arch = amd64 cpu_count = 4 goroutines = 117 max_procs = 4 os = freebsd version = go1.17.8 serf_lan: coordinate_resets = 0 encrypted = true event_queue = 0 event_time = 689 failed = 0 health_score = 0 intent_queue = 0 left = 0 member_time = 63566 members = 14 query_queue = 0 query_time = 1 serf_wan: coordinate_resets = 0 encrypted = true event_queue = 0 event_time = 1 failed = 0 health_score = 0 intent_queue = 0 left = 0 member_time = 15379 members = 5 query_queue = 0 query_time = 1 ```

Operating system and Environment details

FreeBSD 13.0-RELEASE-p8 x64 (installed in jail)

Log Fragments

Apr 21 14:30:56 consul3 consul[71313]: 2022-04-21T14:30:56.286+0200 [ERROR] agent.http: Request error: method=GET url=/v1/discovery-chain/myservice?dc=mydc from=xxx.xxx.xxx.xxx:59204 error="Connect must be enabled in order to use this endpoint"

Amier3 commented 2 years ago

Hey @Peter2121

Thanks for bringing this to our attention. We'll take a look at this and let you know what we find