apache / apache/cloudstack

Dont' show udp protocol for LB rules if the provider is Virtual Router

Open
#13,685 0 comments 1 reaction 0 assignees View on GitHub
component:networking
Dominant language
Java
Stars
3.1k
Forks
1.4k
Avg merge
6d 19h
Merged PRs (30d)
32

Description

### problem

Dont' show udp protocol for LB rules if the provider is Virtual Router

### versions

ACS 4.22.1

### The steps to reproduce the bug

1. Create an isolated network with network offering where LB is set to Virtual Router

Image

2. Navigate Network > public ip address > create a LB > Select UDP proctocol > ADD a instance

Image

Image

3. Currently UDP protocol is not supported by HA PROXY tool( version - 2.6.12) , whichis responsible for creating LB rules.

Image

HA Proxy supports UDP only in the commercial verison https://www.haproxy.com/documentation/haproxy-enterprise/

```
root@r-61-VM:~# cat /etc/haproxy/haproxy.cfg
global
log 127.0.0.1:3914 local0 info
chroot /var/lib/haproxy
user haproxy
group haproxy
daemon

defaults
log global
mode tcp
option dontlognull
retries 3
option redispatch
option forwardfor
stats enable
stats uri /admin?stats
stats realm Haproxy\ Statistics
stats auth admin1:AdMiN123
option httpclose
timeout connect 5000
timeout client 50000
timeout server 50000

listen cloud-default
bind 0.0.0.0:35999
option transparent
root@r-61-VM:~# ps -ef |grep haproxy
root 2062 1 0 15:06 ? 00:00:00 /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -S /run/haproxy-master.sock
haproxy 2092 2062 0 15:06 ? 00:00:00 /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -S /run/haproxy-master.sock


```

### What to do about it?

Don't show udp protocol when creating LB rule in case of Virtual router

Contributor guide

Open the contributing guide

Research direction

Start from Network > public IP address > create a LB and reproduce the provider-specific protocol choices with Virtual Router selected. Confirm the UDP option is absent for Virtual Router while supported options remain available, then verify the resulting load-balancer creation flow still works.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
cloud, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.