zaza-smoke-test: gateway address unavailable

Bug #2024172 reported by James Page
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juju Charmed Operator - Placement K8S
New
Undecided
Unassigned

Bug Description

Seen across a few charms now:

Model Controller Cloud/Region Version SLA Timestamp
zaza-424fc578b7e7 microk8s microk8s/localhost 3.2.0 unsupported 09:35:27Z

App Version Status Scale Charm Channel Rev Address Exposed Message
glance waiting 1 glance-k8s 0 10.152.183.184 no installing agent
keystone waiting 1 keystone-k8s 2023.1/edge 111 10.152.183.135 no installing agent
mysql 8.0.32-0ubuntu0.22.04.2 active 1 mysql-k8s 8.0/stable 75 10.152.183.197 no Primary
rabbitmq 3.9.13 active 1 rabbitmq-k8s 3.9/edge 23 10.170.0.1 no
traefik 2.9.6 waiting 1 traefik-k8s 1.0/stable 110 10.152.183.44 no installing agent
traefik-public 2.9.6 waiting 1 traefik-k8s 1.0/stable 110 10.152.183.147 no installing agent

Unit Workload Agent Address Ports Message
glance/0* waiting idle 10.1.78.138 (ingress-internal) integration incomplete
keystone/0* waiting executing 10.1.78.142 (ingress-internal) integration incomplete
mysql/0* active idle 10.1.78.145 Primary
rabbitmq/0* active idle 10.1.78.148
traefik-public/0* waiting idle 10.1.78.147 gateway address unavailable
traefik/0* waiting idle 10.1.78.149 gateway address unavailable

this blocks the completion of the deployment or breaks testing in someway.

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.