Comment 10 for bug 1971841

Revision history for this message
Alan Baghumian (alanbach) wrote :

@Alex

You do have a valid point! Going back to the command history, I had used channel 2.0.3 and not 2.4 (later refreshed to 2.4) and jammy is not supported on that channel:

$ juju deploy --series jammy --channel 2.0.3/stable hacluster test-hacluster
ERROR series "jammy" not supported by charm, supported series are: focal, bionic. Use --force to deploy the charm anyway.

It does not help that juju info also does not show jammy:

$ juju info hacluster
name: hacluster
publisher: OpenStack Charmers
summary: Corosync Cluster Engine - membership, messaging and quorum
description: |
  Corosync/Pacemaker
store-url: https://charmhub.io/hacluster
charm-id: BVNheXef1exOfCMnIeBV7KP901K2sXKM
supports: xenial, bionic, focal, groovy, hirsute, impish
subordinate: true
relations:
  provides:
    ha: hacluster
    nrpe-external-master: nrpe-external-master
  requires:
    juju-info: juju-info
    pacemaker-remote: pacemaker-remote
    peer-availability: juju-info
channels: |
  latest/stable: 83 2022-02-09 (83) 320kB
  latest/candidate: ↑
  latest/beta: ↑
  latest/edge: 118 2023-03-01 (118) 437kB
  2.4/stable: 120 2023-05-30 (120) 433kB
  2.4/candidate: ↑
  2.4/beta: ↑
  2.4/edge: ↑
  2.0.3/stable: 113 2022-10-04 (113) 430kB
  2.0.3/candidate: ↑
  2.0.3/beta: ↑
  2.0.3/edge: ↑
  1.1.18/stable: –
  1.1.18/candidate: –
  1.1.18/beta: –
  1.1.18/edge: 83 2022-03-04 (83) 320kB

Perhaps, it would be helpful to add a small note in the charm summary or description outlining this.