Fix the ServiceAddress update in Transport server and Virtual Server

[pmaddev]

Environment

• Application Services Version: 3.52.0
• BIG-IP Version: 17.1

Summary

The customer encountered a problem when a TransportServer object without serviceAddress parameter initially. And was updated with new serviceAddress parameter being customized. As a result, the BIG-IP systems would fail to process the declaration.

Steps To Reproduce

When the customer first applied the TransportServer object, there was no 'serviceAddress' parameter.

1. Configure as per the below config for reference
apiVersion: [cis.f5.com/v1](https://cis.f5.com/v1)
kind: TransportServer
metadata:
annotations:
labels:
f5cr: "true"
name: ts-nginx-test1
namespace: kube-system
spec:
bigipRouteDomain: 0
ipamLabel: Default
mode: standard
pool:
monitor:
interval: 20
timeout: 10
type: tcp
service: nginx-test1
serviceNamespace: default
servicePort: 80
snat: auto
type: tcp
virtualServerPort: 8081

2. Observe the following error response:

When the customer attmepted to update the TransportServer object, they included the 'serviceAddress' parameter to allow route advertisement.
apiVersion: [cis.f5.com/v1](https://cis.f5.com/v1)
kind: TransportServer
metadata:
annotations:
labels:
f5cr: "true"
name: ts-nginx-test1
namespace: kube-system
spec:
bigipRouteDomain: 0
ipamLabel: Default
mode: standard
serviceAddress：
- routeAdvertisement: enable
pool:
monitor:
interval: 20
timeout: 10
type: tcp
service: nginx-test1
serviceNamespace: default
servicePort: 80
snat: auto
type: tcp
virtualServerPort: 8081

Errors:
The error log messages reported by restnoded process on the BIG-IP system are like the following example:
Thu, 05 Dec 2024 07:30:06 GMT - severe: [appsvcs] {"message":"Declaration failed: 0107176c:3: Invalid Virtual Address, the IP address 10.9.249.101 already exists.","level":"error"}

Expected Behavior

It should not throw any error while adding the new customized serviceAddress to the TS/VS object
It should not throw any error while updating the existed serviceAddress on the TS/VS object
It should not throw any error while deleting the existed serviceAddress from the TS/VS object

Actual Behavior

Its throwing an error and not allowed to configure the serviceAddress to the TS/VS object, please refer the errors section.