On units with VIP(s) assigned by ha-cluster private-address returns the VIP instead of the unit IP

Bug #1898846 reported by Diko Parvanov
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju

Bug Description

On an occasion with kubernetes-master charm related to vault charm - the vault charm received an 'access-address' the unit proper IP address but for 'private-address' the unit VIP address. This was only fixed by moving the VIP to a working unit, removing the already deployed unit and re-adding a new unit that properly reports the private-address, without having the VIP added as second IP to the primary interface. Juju version: 2.7.4

Revision history for this message
John A Meinel (jameinel) wrote :

Given this is a case of having the wrong private address, I'm going to mark it a dupe of 1897115. It is possible there are other ways that this could be happening, but I think the fixes there will likely address this as well.

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.