-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenShift: Creating and deleting of TransportServers with F5 CIS Operator Version 2.18.1-ubi9
not working
#3660
Comments
@keennessch Please share sample transport server resources and complete CIS logs to [email protected] |
i too have the same issue i'm running OCP 4.14.12 please find the arguments i'm using for CIS
please find the transportserver configuration
|
I'm also experiencing this issue. I've emailed the logs as requested. |
@abvinodu2003 Please share sample transport server resources and complete CIS logs to [email protected] |
This works fine on 2.18.0 but not on 2.18.1 |
Created [CONTCNTR-5007] for internal tracking. |
Fixed in 2.19 |
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 to
2.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
.spec.version
field to2.18.1-ubi9
in the F5BigIpCtlr resource on the OCP clusterExpected 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
[...]
.The text was updated successfully, but these errors were encountered: