"juju info" missing revision in the list

[Felipe Reyes]

We have a build of the mysql-router charm that was released 1 hour[0] before the data samples shared here, this upload was marked as revision 30 by the store in the 8.0/edge track, where checking "charmcraft status mysql-router" is there (see https://pastebin.canonical.com/p/GXWbt5J7j6/ ), while the command "juju info mysql-router --channel 8.0 --series jammy --arch amd64" is still reporting the revision 26 for the 8.0/edge track (see https://pastebin.canonical.com/p/VPvCsZTcp9/ )

Querying the charmhub's api directly returns the expected revision 30

 ~ $ curl -s https://api.charmhub.io/v2/charms/info/mysql-router?fields=channel-map,channel-map.revision | jq '."channel-map" |. [] | select(.channel.risk == "edge" and .channel.track == "8.0" and .channel.base.architecture == "amd64" and .channel.base.channel == "22.04") |.revision.revision'
30

Running juju deploy does find revision 30, so this seems to be constrained to the code behind "juju info".

 ~ $ juju deploy --series jammy --channel 8.0/edge mysql-router
Located charm "mysql-router" in charm-hub, revision 30
Deploying "mysql-router" from charm-hub charm "mysql-router", revision 30 in channel 8.0/edge on jammy

[0] https://launchpad.net/~openstack-charmers/charm-mysql-router/+charm/charm-mysql-router.stable-jammy.8.0.19/+build/2473

[Juan M. Tirado (tiradojm)]

The problem appears when using the --channel selector with the query. When the selector is not used the retrieved information is correct. See https://pastebin.canonical.com/p/CBpCnRKYNp/

This could be related with the fact that charmhub returns the list of found entries in incremental order

curl -s https://api.charmhub.io/v2/charms/info/mysql-router?fields=channel-map,channel-map.revision | jq '."channel-map" |. [] | select( .channel.track == "8.0" ) |.revision.revision'

[Heather Lanigan (hmlanigan)]

@freyes,

Which version of juju are you using? Changes were recently made to juju info for this bug: https://bugs.launchpad.net/juju/+bug/1967850

[Felipe Reyes (freyes)]

On Mon, 2022-06-06 at 17:40 +0000, Heather Lanigan wrote:
> @freyes,
>
> Which version of juju are you using?

Assuming this feature is purely a client side implementation:

 ~ $ juju info mysql-router --channel 8.0 --series jammy --arch amd64
name: mysql-router
charm-id: CjjVf4bSJGT6rKjg7Qk3EZteCoEhKXHh
summary: MySQL Router
publisher: OpenStack Charmers
supports: focal, jammy
tags: cloud, databases
subordinate: true
store-url: https://charmhub.io/mysql-router
description: |
  MySQL Router proxying communication between application clients and MySQL
InnoDB Clusters.
relations:
  provides:
    shared-db: mysql-shared
  requires:
    certificates: tls-certificates
    db-router: mysql-router
    juju-info: juju-info
channels: |
  8.0/stable: 18cff04 2022-05-19 (26) 14MB
  8.0/candidate: ↑
  8.0/beta: ↑
  8.0/edge: ↑

 ~ $ juju --version
2.9.32-ubuntu-amd64
 ~ $ snap info juju | grep installed
installed: 2.9.32-8e83c2b (19590) 97MB classic

> Changes were recently made to juju
> info for this bug: https://bugs.launchpad.net/juju/+bug/1967850
>
should this be in 2.9.32? or should I test a different track?

[Ian Booth (wallyworld)]

This looks to be fixed?

$juju version
2.9.32-ubuntu-amd64

$ juju info mysql-router --channel 8.0 --series jammy --arch amd64
name: mysql-router
charm-id: CjjVf4bSJGT6rKjg7Qk3EZteCoEhKXHh
summary: MySQL Router
publisher: OpenStack Charmers
supports: focal, jammy
tags: cloud, databases
subordinate: true
store-url: https://charmhub.io/mysql-router
description: |
  MySQL Router proxying communication between application clients and MySQL InnoDB Clusters.
relations:
  provides:
    shared-db: mysql-shared
  requires:
    certificates: tls-certificates
    db-router: mysql-router
    juju-info: juju-info
channels: |
  8.0/stable: 7488ce1 2022-06-13 (30) 14MB
  8.0/candidate: ↑
  8.0/beta: ↑
  8.0/edge: ↑

I'll mark as incomplete and we can reopen if needed.