Open keennessch opened 4 days ago
@keennessch Please share sample transport server resources and complete CIS logs to automation_toolchain_pm@f5.com
i too have the same issue i'm running OCP 4.14.12 please find the arguments i'm using for CIS
args: [
"--bigip-username=$(BIGIP_USERNAME)",
"--bigip-password=$(BIGIP_PASSWORD)",
"--bigip-url=192.168.110.167",
"--bigip-partition=ocpclusterpart",
"--pool-member-type=cluster",
"--log-level=AS3DEBUG",
"--insecure=true",
"--as3-validation=true",
"--log-as3-response=true",
"--static-routing-mode=true",
"--orchestration-cni=ovn-k8s",
"--agent=as3",
"--custom-resource-mode=true",
]
please find the transportserver configuration
[cislogs.txt](https://github.com/user-attachments/files/17949850/cislogs.txt)
I'm also experiencing this issue. I've emailed the logs as requested.
Setup Details
CIS Version : 2.18.1 Build: registry.connect.redhat.com/f5networks/cntr-ingress-svcs:2.18.1-ubi9 BIGIP Version: BIG-IP 17.1.1.3 Build 0.21.5 Engineering Hotfix AS3 Version: 3.48.0 Agent Mode: AS3 Orchestration: OSCP Orchestration Version: 4.16.17 Pool Mode: Cluster Additional Setup details:
Description
After updating the F5 CIS Operator to
2.18.1-ubi9
, existing TransportServer resources change toPending
status. New TransportServers immediately showPending
status, stay in this state and are never created on the load balancer. Deleting TransportServer resources are deleted from the OpenShift cluster but not from the load balancer. Switching the Operator's version back to2.18.0-ubi9
by defining it in the.spec.version
field of the F5BigIpCtlr resource, TransportServer resources change toOk
status after a couple of seconds. Creating and deleting TransportServers works as expected and have the desired effect on the load balancer.Steps To Reproduce
1) Change the
.spec.version
field to2.18.1-ubi9
in the F5BigIpCtlr resource on the OCP cluster 2) Wait for the new f5-bigip-ctlr pod to successfully startExpected Result
TransportServer resources show the correct state corresponding to their virtual server counterparts on the load balancer. New TransportServer resources can be created and show up as virtual servers on the load balancer. Existing TransportServer resources can be deleted and are deleted on the load balancer.
Actual Result
TransportServer resources show
Pending
state, regardless of their actual state on the load balancer. New TransportServer resources can be created on the OCP cluster but are not created on the load balancer. Existing TransportServer resources can be deleted on the OCP cluster but are not deleted on the load balancer.Diagnostic Information
The used F5BigIpCtlr definition while collecting logs for this issue:
Logs from the f5-bigip-ctlr pod. Repeating lines have been replaced by
[...]
.