Cannot install mysql-router

Bug #1884460 reported by Michael Quiniola
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MySQL Router Charm
Fix Released
Critical
Unassigned

Bug Description

Trying to transition from MySQL5 to MySQL8 with the mysql-innodb-cluster.

All charms have been upgraded to Focal (20.04), all (current) charms needing the mysql-routers are in LXC's and upgraded to the newest version.

After the process here (https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/app-series-upgrade-specific-procedures.html#percona-cluster-charm-series-upgrade-to-focal), I relate the appropriate mysql-router to the charm (i.e. keystone to keystone-mysql-router. I receive this error:

Juju shows "Hook failed: install"

logs show:

2020-06-21 21:16:16 DEBUG install ERROR: Command errored out with exit status 1:
2020-06-21 21:16:16 DEBUG install command: /var/lib/juju/agents/unit-keystone-mysql-router-1/.venv/bin/python /var/lib/juju/agents/unit-keystone-mysql-router-1/.venv/lib/python3.8/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-t_vsw7hs/overlay --no-warn-script-location --no-binary :none: --only-binary :none: --no-index --find-links wheelhouse -- 'setuptools>=30.3' wheel 'setuptools_scm[toml]>=3.4.1'
2020-06-21 21:16:16 DEBUG install cwd: None
2020-06-21 21:16:16 DEBUG install Complete output (5 lines):
2020-06-21 21:16:16 DEBUG install Looking in links: wheelhouse
2020-06-21 21:16:16 DEBUG install Processing /root/.cache/pip/wheels/ee/7f/10/5201bcf514a2a7b9bf607440e3c23d5b3957dc8b2f97db315c/setuptools-41.6.0-py2.py3-none-any.whl
2020-06-21 21:16:16 DEBUG install Processing /root/.cache/pip/wheels/da/cb/b0/81460926f07d2d44880273cdf314a667ed615e9e5165bc41a1/wheel-0.33.6-py2.py3-none-any.whl
2020-06-21 21:16:16 DEBUG install ERROR: Could not find a version that satisfies the requirement setuptools_scm[toml]>=3.4.1 (from versions: 1.17.0)
2020-06-21 21:16:16 DEBUG install ERROR: No matching distribution found for setuptools_scm[toml]>=3.4.1

This is work stoppage and will have to return to MySQL5 until a workaround/fix is found.

description: updated
description: updated
Revision history for this message
Luis Felipe Domínguez Vega (luis.dominguez) wrote :

I think that packages inside wheelhouse are too old

Revision history for this message
James Page (james-page) wrote :

layer basic is comparing the system installed python3-setuptools-scm with the version provided in the wheelhouse (1.17.0) and deciding to pick the one installed on the system - however the charm does not use system installed modules so this call them fails.

Revision history for this message
Luis Felipe Domínguez Vega (luis.dominguez) wrote :

In a code review, i think that this charm is very outdated???? This dont work on focal...

Revision history for this message
James Page (james-page) wrote :

I suspect this is a side-effect of the upgrade path your deployment has been through that we've not seen in upgrade testing but its still a bug.

Revision history for this message
James Page (james-page) wrote :
Revision history for this message
Michael Quiniola (qthepirate) wrote :

@james-page actually, i made an attempt to add a brand new unit (LXC) with new series (inclusing relation) with the exact same result.

tags: added: series-upgrade
Revision history for this message
Luis Felipe Domínguez Vega (luis.dominguez) wrote :

Me too... i rollback to use my old percona-cluster

Revision history for this message
Luis Felipe Domínguez Vega (luis.dominguez) wrote :

Using new LXC has same behavior

Changed in charm-mysql-router:
status: New → Confirmed
Revision history for this message
Michael Quiniola (qthepirate) wrote :

Is there a workaround? Maybe have the system install the same version as whats in the wheelhouse that way they stay the same?

Frode Nordahl (fnordahl)
Changed in charm-mysql-router:
importance: Undecided → Critical
assignee: nobody → Frode Nordahl (fnordahl)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-mysql-router (stable/20.05)

Fix proposed to branch: stable/20.05
Review: https://review.opendev.org/737683

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-mysql-router (stable/20.05)

Reviewed: https://review.opendev.org/737683
Committed: https://git.openstack.org/cgit/openstack/charm-mysql-router/commit/?id=62c5940ec199d29caf80a0b1db493d19234273f9
Submitter: Zuul
Branch: stable/20.05

commit 62c5940ec199d29caf80a0b1db493d19234273f9
Author: Frode Nordahl <email address hidden>
Date: Wed Jun 24 08:08:38 2020 +0200

    Stable rebuild to fix dependency issue

    The charm in the store has regressed due to a change in a upstream
    dependency.

    This issue was fixed by pinning said dependency in layer-basic [0].

    0: https://github.com/juju-solutions/layer-basic/pull/179

    Move pinning of stable deps to wheelhouse-override as the current
    approach adds both versions and the one with the newest version
    will be used.

    Add explicit netaddr pin in wheelhouse-override as the order of
    dependencies may override the one consumed from layer-basic.

    Change-Id: I33d7f81319cd3515d4dac9a91b001281d3155bbf
    Closes-Bug: #1884460

Frode Nordahl (fnordahl)
Changed in charm-mysql-router:
status: In Progress → Fix Released
milestone: none → 20.05
assignee: Frode Nordahl (fnordahl) → nobody
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.