You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Hi, I have installed the citrix-ingress-controller in my Kubernetes cluster and when trying to create an Ingress it throws an error of: 2022-08-06 10:09:20,721 - ERROR - [nitrointerface.py:_create_nsapp_cs_vserver:3575] (MainThread) Failed to create csvserver <prefix-frontend-ip_80_http> errorcode=273,message=Resource already exists
In the UI I can't see that the server exists, so I'm not sure whats going on.
I also tried to change the NS_APPS_NAME_PREFIX to make sure it definitely doesn't exist but that doesn't help either.
To Reproduce
citrix-k8s-ingress-controller:1.26.7
Ingress:
@ONordander By any chance are you using the same frontend-ip in ingresses belonging to different controllers?
We currently don't support sharing the same frontend-ip by multiple ingress controllers.
Describe the bug
Hi, I have installed the citrix-ingress-controller in my Kubernetes cluster and when trying to create an Ingress it throws an error of:
2022-08-06 10:09:20,721 - ERROR - [nitrointerface.py:_create_nsapp_cs_vserver:3575] (MainThread) Failed to create csvserver <prefix-frontend-ip_80_http> errorcode=273,message=Resource already exists
In the UI I can't see that the server exists, so I'm not sure whats going on.
I also tried to change the
NS_APPS_NAME_PREFIX
to make sure it definitely doesn't exist but that doesn't help either.To Reproduce
citrix-k8s-ingress-controller:1.26.7
Ingress:
Expected behavior
No errors and a successful creation of CS VServer.
Logs
2022-08-06 10:09:20,721 - ERROR - [nitrointerface.py:_create_nsapp_cs_vserver:3575] (MainThread) Failed to create csvserver <prefix-frontend-ip_80_http> errorcode=273,message=Resource already exists
Additional context
I'm running multiple ingress-controllers in different clusters if that might give any indication.
The text was updated successfully, but these errors were encountered: