Question: why charm "mysql" ignores "issues" attribute in metadata.yaml

charmhub requests
,
1

Hi,

Question: why “mysql charm” shows “Submit a bug” as https://github.com/juju-solutions/charm-mysql/issues IF metadata.yaml uses “issues: https://github.com/canonical/mysql-operator/issues”.

P.S. it is to address https://github.com/canonical/mysql-operator/issues/54 P.P.S. I do not see the link https://github.com/juju-solutions/charm-mysql/issues in old charm-mysql/metadata.yaml too.

Tnx for hints!

2

Hey there,

Guillermo looked at the yaml from the current revision and it looks weird, there are some single-quote issues, the “description” multiline attribute is wrongly formatted, and there’s an incomplete single-quote before the “maintainers” field.

assumes:
- juju
description: 'MySQL charm for machines

  '
display-name: MySQL
issues: 'https://github.com/canonical/mysql-operator/issues

  This charm supports MySQL 8 on machines.'
maintainers:
- Paulo Machado <paulo.machado@canonical.com>
- Shayan Patel <shayan.patel@canonical.com>
name: mysql
peers:
  database-peers:
    interface: mysql_peers
provides:
  cos-agent:
    interface: cos_agent
    limit: 1
  database:
    interface: mysql_client
  db-router:
    interface: mysql-router
  mysql:
    interface: mysql
  shared-db:
    interface: mysql-shared
requires:
  certificates:
    interface: tls-certificates
    limit: 1
  s3-parameters:
    interface: s3
    limit: 1
source: https://github.com/canonical/mysql-operator
storage:
  database:
    description: Persistent storage for MySQL data
    location: /var/snap/charmed-mysql/common/var/lib/mysql
    type: filesystem
summary: 'MySQL is a widely used, open-source relational database management system

  (RDBMS). MySQL InnoDB cluster provides a complete high availability solution

  for MySQL via Group Replication.

  '

parsing it, the issues value looks like this (verbatim, I mean this is what the yaml parsing library returns when asked for the “issues” field, you can see it contains a bunch of extraneous text).

issues: https://github.com/canonical/mysql-operator/issues

  This charm supports MySQL 8 on machines.
maintainers:
  - Paulo Machado <paulo.machado@canonical.com>
  - Shayan Patel <shayan.patel@canonical.com>

Thus the link does not validate as a proper URL and does not get updated in the links structure in the database.

If you fix your YAML and upload and publish a new build, this should update correctly.

  • Daniel
3

Dear @roadmr,

Thank you for your findings! I have prepared PR to update it (as also “summary” must be a single line).

4

Dear @roadmr,

I have fixed metadata.yaml in https://github.com/canonical/mysql-operator/pull/201, merged and released to 8.0/stable. Unfortunately the bugreport link is still wrong on http://charmhub.io/mysql (is it somehow related to closed latest and not yet-moved default track?

Thank you for any hints!

5

Hi - I’ve just set up the default tracks. Could you please re-release the same revision to 8.0/stable and let me know if it updates correctly?

Thanks!

  • Daniel
6

Confirmed. Re-release the same version fixed links. Thank you! The topic can be closed.

7

Just for the issues linking, the same story with PostgreSQL charm reported here: https://github.com/canonical/charmhub.io/issues/1591

Re-relesing the same revision to 14/stable doesn’t help. I suspect it is due to not-yet closed latest/stable.