Bug Description
The charm can enter a blocked state with the message Missing 'gateway-route' relation even when a gateway-route relation is present. Checking juju debug-log shows Required field(s) are missing, skipping update of the relation data. is the actual cause. Setting the hostname config option once the relation exists moves the charm into the active state.
This is somewhat confusing given that the relation exists as far as Juju is concerned, it's just that the information on the charm side is incomplete. I think it would be more helpful to identify this and provide a different status message, such as Incomplete 'gateway-route' relation or hostname config required.
Impact
Low (minor issue or cosmetic problem)
Impact Rationale
No response
To Reproduce
juju deploy --trust gateway-api-integrator --channel latest/edge --revision 147juju deploy gateway-route-configurator --channel latest/edge --revision 12 backend-gateway-configurator
At this stage, the charm will be blocked with the message Missing 'ingress' relationjuju relate gateway-route-configurator <ingress-requirer-charm>
At this stage the charm will be blocked with the message Missing 'gateway-route' relationjuju relate gateway-api-integrator gateway-route-configurator
At this stage, the charm remains blocked with the message MMissing 'gateway-route' relation, but the debug log will reveal the Required field(s) are missing, skipping update of the relation data. message.
Environment
I am running on a Canonical Kubernetes cluster which is in an environment internal to Canonical. As shown in the steps above, I am using revision 12 from the latest/edge channel.
Relevant log output
unit-backend-gateway-configurator-0: 21:30:37 INFO juju.worker.uniter.operation ran "gateway-route-relation-created" hook (via hook dispatching script: dispatch)
unit-backend-gateway-configurator-0: 21:30:37 INFO juju.worker.uniter.operation ran "gateway-route-relation-joined" hook (via hook dispatching script: dispatch)
unit-backend-gateway-configurator-0: 21:30:38 WARNING unit.backend-gateway-configurator/0.juju-log gateway-route:180: Required field(s) are missing, skipping update of the relation data.
unit-backend-gateway-configurator-0: 21:30:38 INFO juju.worker.uniter.operation ran "gateway-route-relation-changed" hook (via hook dispatching script: dispatch)
Additional context
No response
Bug Description
The charm can enter a
blockedstate with the messageMissing 'gateway-route' relationeven when agateway-routerelation is present. Checkingjuju debug-logshowsRequired field(s) are missing, skipping update of the relation data.is the actual cause. Setting thehostnameconfig option once the relation exists moves the charm into theactivestate.This is somewhat confusing given that the relation exists as far as Juju is concerned, it's just that the information on the charm side is incomplete. I think it would be more helpful to identify this and provide a different status message, such as
Incomplete 'gateway-route' relationorhostname config required.Impact
Low (minor issue or cosmetic problem)
Impact Rationale
No response
To Reproduce
juju deploy --trust gateway-api-integrator --channel latest/edge --revision 147juju deploy gateway-route-configurator --channel latest/edge --revision 12 backend-gateway-configuratorAt this stage, the charm will be
blockedwith the messageMissing 'ingress' relationjuju relate gateway-route-configurator <ingress-requirer-charm>At this stage the charm will be
blockedwith the messageMissing 'gateway-route' relationjuju relate gateway-api-integrator gateway-route-configuratorAt this stage, the charm remains
blockedwith the messageMMissing 'gateway-route' relation, but the debug log will reveal theRequired field(s) are missing, skipping update of the relation data.message.Environment
I am running on a Canonical Kubernetes cluster which is in an environment internal to Canonical. As shown in the steps above, I am using revision 12 from the latest/edge channel.
Relevant log output
Additional context
No response