After resizing traefik does not extend units to more backends

Bug #2028364 reported by Bartosz Woronicz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Snap
Triaged
High
Unassigned

Bug Description

Scenario
- bootstrap with --accept-defaults
- add node with just control and compute role
- add node with just control and compute role

sunbeam cluster resize
and wait for the end of it

monitor api with
while true; do openstack server list && echo OK; done

kill keystone-0 pod
and it takes 1min around to have the API back

Seems that Traefik loadbalancer got just one server backend

ubuntu@node08:~$ kubectl exec -n openstack -c traefik -t traefik-0 -- cat /opt/traefik/juju/juju_ingress_
ingress_49_keystone.yaml
http:
….
     domains:
     - main: 10.20.21.12
       sans:
       - '*.10.20.21.12'
  services:
 juju-openstack-keystone-service:
   loadBalancer:
     servers:
     - url: http://keystone-0.keystone-endpoints.openstack.svc.cluster.local:5000

and that is true also for traefik-1 and traefik-2

description: updated
Revision history for this message
James Page (james-page) wrote :

This is a bug in the ingress v1 interface - its not actually providing IngressPerApp as the leader unit populates the app databag with its FQDN, rather than that of the K8S service it sits behind.

The ingress v2 interface has the right behaviour but is currently only in the traefik/edge channel.

Changed in snap-openstack:
status: New → Confirmed
importance: Undecided → High
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.