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
It seems that HCCM is not able to see that a certificate already exists (already created by HCCM from a re-created Service or from another Service).
If it already exists then it fails and the Services in the load balancer are not produced
Expected behavior
I expect HCCM not to fail if the certificate already exists and was created by itself.
Observed behavior
When I create the Service (annotations below) for the first time I can see the new certificate in the Hetzner Certificate section
Due to that I can see that HCCM populates even the Services section of my Hetzner Load Balancer. Everything works fine
If i destroy and recrete my service, than HCCM reports these errors
E0803 16:54:50.345120 1 controller.go:298] error processing service traefik/traefik (retrying with exponential backoff): failed to ensure load balancer: hcloud/loadBalancers.EnsureLoadBalancer: hcops/LoadBalancerOps.ReconcileHCLBServices: hcops/hclbServiceOptsBuilder.buildAddServiceOpts: hcops/CertificateOps.GetCertificateByLabel: not found
I0803 16:54:50.345206 1 event.go:389] "Event occurred" object="traefik/traefik" fieldPath="" kind="Service" apiVersion="v1" type="Warning" reason="SyncLoadBalancerFailed" message="Error syncing load balancer: failed to ensure load balancer: hcloud/loadBalancers.EnsureLoadBalancer: hcops/LoadBalancerOps.ReconcileHCLBServices: hcops/hclbServiceOptsBuilder.buildAddServiceOpts: hcops/CertificateOps.GetCertificateByLabel: not found"
Seems like it can't detect that the certificate already exists and it fails.
If I delete the certificate nothing more happens but then If I delete and re-create the Service so HCCM "wake up" and recreated the certificate correctly (with Services in LB).
It sounds like a good workaround but, in fact, is a workaround. No?
It sounds no-sense that I have to "patch" the label of the exist certificate every time I re create the Service
TL;DR
It seems that HCCM is not able to see that a certificate already exists (already created by HCCM from a re-created Service or from another Service).
If it already exists then it fails and the Services in the load balancer are not produced
Expected behavior
I expect HCCM not to fail if the certificate already exists and was created by itself.
Observed behavior
When I create the Service (annotations below) for the first time I can see the new certificate in the Hetzner Certificate section
Due to that I can see that HCCM populates even the Services section of my Hetzner Load Balancer. Everything works fine
If i destroy and recrete my service, than HCCM reports these errors
Seems like it can't detect that the certificate already exists and it fails.
If I delete the certificate nothing more happens but then If I delete and re-create the Service so HCCM "wake up" and recreated the certificate correctly (with Services in LB).
Minimal working example
Services with these annotations
Log output
The text was updated successfully, but these errors were encountered: