bug: Error during consul discovery synchronization when port field is missing in Consul service

[zkx5xkt]

Current Behavior

When Consul discovery is enabled, an error occurs during service synchronization from Consul (attempt to concatenate local 'svc_port' (a nil value)) if not all services in Consul contain the port field.
This leads to the issue where APISIX Consul discovery does not add any services at all.

The error happens here

Expected Behavior

In Consul, the only mandatory field when registering a service is name. Therefore, services that cannot be added to the APISIX discovery should be skipped.

Error Logs

2025/02/10 03:57:40 [error] 32#32: *54 lua entry thread aborted: runtime error: /usr/local/apisix/apisix/discovery/consul/init.lua:525: attempt to concatenate local 'svc_port' (a nil value)

Steps to Reproduce

1. run consul, register service only with name provided
2. enable consul discovery in apisix
3. run apisix via docker image

Environment

• APISIX version (run apisix version): 3.11.0
• Operating system (run uname -a):
• OpenResty / Nginx version (run openresty -V or nginx -V):
• etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info):
• APISIX Dashboard version, if relevant:
• Plugin runner version, for issues related to plugin runners:
• LuaRocks version, for installation issues (run luarocks --version):

[bzp2010]

This means that this node needs to be skipped when the Consul response does not contain the port or any of the fields we need, right?

[zkx5xkt]

I think so, I believe this is the expected behavior: if there's no way to route to this service, it won't be added as a candidate.

[Baoyuantop]

Duplicate of #11134

And we have a fix in #12304.

Hi @zkx5xkt, in this fix, if port is nil, we will set a default 80 port, what do you think of this?