MySQL InnoDB Cluster Charm

CI failure(s) because there is a mismatch between python-libjuju version and the juju controller

Bug #2056787 reported by Felipe Reyes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL InnoDB Cluster Charm
In Progress
Undecided
Unassigned
MySQL Router Charm
New
Undecided
Unassigned

Bug Description

Zaza gained support for juju-3.x, as a consequence it lifted the pinning of python-libjuju. Downstream consumers (e.g. charm-mysql-innodb-cluster) are expected to configure their CI environment with a combination that satisfy the constraints that python-libjuju.

Felipe Reyes (freyes)
Changed in charm-mysql-innodb-cluster:
status: New → Triaged
tags: added: unstable-test
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-mysql-innodb-cluster (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/charm-mysql-innodb-cluster/+/912487

Changed in charm-mysql-innodb-cluster:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-mysql-innodb-cluster (master)

Change abandoned by "Felipe Reyes <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/charm-mysql-innodb-cluster/+/912487
Reason: Pinning zaza to juju<3.0.0 - https://github.com/openstack-charmers/zaza/pull/652

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.