** Changed in: charm-nova-compute
Milestone: 17.08 => None
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1657305
Title:
percona cluster getting wrong private ip
To manage
** Changed in: charm-nova-compute
Milestone: 17.05 => 17.08
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1657305
Title:
percona cluster getting wrong private ip
To manage
** Changed in: charm-percona-cluster
Status: New => Fix Released
** Changed in: charm-percona-cluster
Milestone: None => 17.02
** Changed in: charm-nova-compute
Milestone: None => 17.05
** Changed in: charm-percona-cluster
Importance: Undecided => High
** Changed in:
** Changed in: percona-cluster (Juju Charms Collection)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1657305
Title:
percona cluster getting
** Changed in: charm-nova-compute
Importance: Undecided => High
** Changed in: charm-nova-compute
Status: New => Triaged
** Changed in: nova-compute (Juju Charms Collection)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
** Changed in: nova-compute (Juju Charms Collection)
Importance: Critical => High
** Changed in: nova-compute (Juju Charms Collection)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in
** Changed in: percona-cluster (Juju Charms Collection)
Assignee: (unassigned) => James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1657305
Title:
percona
In the scope of the percona-charm, we see two problems:
a) the network space binding for the cluster relation is not being used
for the local wsrep address for mysql (although the cluster relation
space binding is used to build the list of hosts participating in the
cluster). This might not
I appreciate the need to move charms to the network-get --primary-
address charm hook tool to support use of network spaces, but I still
feel that there might be a 'undefined behaviour' use case in this code
path.
If a user does not bind a relation or extra-binding, then what gets
returned from
Larry - for percona-cluster, you'll need to provide a binding for the
shared-db relation to oil as well; no need to use the access-network
configuration option (infact that prevents the use of juju network space
binding in the charm).
--
You received this bug notification because you are a
10 matches
Mail list logo
