[VRO]Egress rule destination ports setting to -1,-1 if port range specified as any
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
Trunk |
Fix Committed
|
High
|
Daniel Jasiński |
Bug Description
Security group work flows
In case of egress rule when port range set to any
In the api server destination ports were setting to -1,-1 instead of 0-65535
In case of ingress rule when port range set to any
In the api server source ports were setting to -1,-1 instead of 0-65535
security_
" policy_rule: [
o {
" direction: ">",
" protocol: "any",
" dst_addresses: [],
" ethertype: "IPv4",
" dst_ports: [
" {
" end_port: -1,
" start_port: -1
}
" ],
" rule_uuid: "d1500e94-
" src_addresses: [
" {
" security_group: "local"
}
" ],
" src_ports: [
" {
" end_port: 65535,
" start_port: 0
}
" ]
o },
o {
" direction: ">",
" protocol: "any",
" dst_addresses: [
" {
" security_group: "local"
}
" ],
" ethertype: "IPv4",
" dst_ports: [
" {
" end_port: 65535,
" start_port: 0
}
" ],
" rule_uuid: "e013f883-
" src_addresses: [],
" src_ports: [
" {
" end_port: -1,
" start_port: -1
}
" ]
o }
information type: | Proprietary → Public |
tags: | added: vmware |