incorrect k8s service address

Bug #1928282 reported by Ian Booth
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Ian Booth
2.9
Fix Released
High
Ian Booth

Bug Description

As reported here https://discourse.charmhub.io/t/how-does-juju-collect-ingress-address/4521

Juju can incorrectly look at the headless service for a deployed app to query the service address info. This results in 2 problems:
- the address value of None is stored instead of the actual IP or hostname
- a mongo txn error can occur depending on the order of the updates

Tags: k8s
Ian Booth (wallyworld)
tags: added: k8s
Revision history for this message
Ian Booth (wallyworld) wrote :
Ian Booth (wallyworld)
Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
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.