Closed sudeephb closed 7 months ago
(by vern) As a temporary workaround, I pulled the charm and deployed from local:
charm pull cs:openstack-service-checks juju deploy ./openstack-service-checks
(by vern) Subscribing field-high as this is affecting a customer deployment. The severity of this would be reduced if the charmhub proxy bug is resolved https://bugs.launchpad.net/juju/+bug/1940327
(by dparv) Why not use ch:openstack-service-checks? Or just openstack-service-checks? The way forward is to use the charmhub, and all latest revisions are published there. AFAIK the charmhub syncs to charmstore, but we are unable to manage the charmstore since charmhub went live and replaced it. This works:
juju deploy ch:openstack-service-checks Located charm "openstack-service-checks" in charm-hub, revision 9 Deploying "openstack-service-checks" from charm-hub charm "openstack-service-checks", revision 9 in channel stable
juju deploy openstack-service-checks --channel stable Located charm "openstack-service-checks" in charm-hub, revision 9 Deploying "openstack-service-checks" from charm-hub charm "openstack-service-checks", revision 9 in channel stable
juju deploy openstack-service-checks Located charm "openstack-service-checks" in charm-hub, revision 9 Deploying "openstack-service-checks" from charm-hub charm "openstack-service-checks", revision 9 in channel stable
with: applications: openstack-service-checks: charm: ch:openstack-service-checks num_units: 1 options: s3_check_params: /
juju deploy ./test.yaml Located charm "openstack-service-checks" in charm-hub, channel stable Executing changes:
With: applications: openstack-service-checks: charm: openstack-service-checks num_units: 1 options: s3_check_params: /
juju deploy ./test.yaml Located charm "openstack-service-checks" in charm-hub, channel stable Executing changes:
(by vern) My deployment is behind a proxy and any charmhub charms time out when connecting to api.charmhub.io. See LP#1940327.
A few people have reported this but I couldn't find a bug for it.
When deploying cs:openstack-service-checks we get:
cs:openstack-service-checks-9 resource "core18": bad metadata: resource missing filename
A simple bundle to reproduce:
applications: openstack-service-checks: charm: cs:openstack-service-checks num_units: 1 options: s3_check_params: /
From roadmr: openstack-service-checks had a release to stable 2 days ago, but whoever did it, didn't associate the resources, so the revisions that are currently on stable do, indeed, not point to a valid resource. This is why it's broken
A proposed workaround is to remove "cs:" so that it pulls the charmhub version instead of the charmstore one but I'm uncertain exactly how the two revisions relate. Some have reported this to work but I have not been able to as I seem to be encountering a proxy bug related to charmhub: LP#1940327
Imported from Launchpad using lp2gh.
date created: 2022-03-12T07:41:01Z
owner: vern
assignee: None
the launchpad url