Juju offline deploy of charmed kubeflow bundle fails

[Gustavo Sanchez]

Juju client offline fails deploying kubeflow

===== Context
Juju Controller: 2.9.45
Juju Cli: 2.9.45 (Air Gapped)
Cloud: AWS EKS (Private / Air Gapped)

Charmed Kubeflow: 1.7
Bundle: https://paste.ubuntu.com/p/7GsMQHcbfk/

===== Description
The first time I try to deploy the bundle it complains with

ERROR cannot deploy bundle: series "kubernetes" not supported by charm, supported series are: focal
02:54:23 DEBUG cmd supercommand.go:537 error stack:
series "kubernetes" not supported by charm, supported series are: focal

After that, second and following times trying to deploy a get a different error message

ERROR cannot deploy bundle: cannot deploy local charm at "/root/workdir/admission-webhook": file does not exist
02:54:35 DEBUG cmd supercommand.go:537 error stack:
file does not exist

===== Details
Execution and Logs -> https://paste.ubuntu.com/p/hxkPFGXMvr/

[Gustavo Sanchez (gustavosr98)]

Subscribing as "field-critical"
Blocking a deployment with a customer

[Joseph Phillips (manadart)]

Based on the logs, you seem to be using a mix charm of metadata V1 and V2.

That would indicate some charms have manifests with bases, and others have metadata with series.

Does it work if your bundle is uniform?

[John A Meinel (jameinel)]

Given current workflows, it is also fairly likely that they are running V1 with manifest.yaml, which is certainly one source of confusion (and likely that metadata.yaml and manifest.yaml don't agree)

[Gustavo Sanchez (gustavosr98)]

Downgrading priority to field-high since there is a workaround
See
[1] https://github.com/canonical/bundle-kubeflow/issues/693
[2] https://github.com/canonical/mysql-k8s-operator/issues/321

[Joseph Phillips (manadart)]

I've marked as invalid for Juju, as a homogeneous bundle with regard to metadata/manifest should work.