oc adm catalog mirror generate bad catalog name and bad image url

[ddcdk]

Oc version
Client Version: 4.16.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: 4.16.2
Kubernetes Version: v1.29.6+aba1e8d

I use this kind of command to mirror an operator to a local registry :
oc adm catalog mirror myregistry.mycompany.com/olm-mirror/web-terminal/web-terminal-index:v4.16 myregistry.mycompany.com/olm-mirror --insecure --continue-on-error --skip-verification --max-components=3

First problem :
This command produce a CatalogSource.yaml file with this wrong metadata name : web-terminal/web-terminal-index
We can not have a '/' in name.

Second problem :
The spec.image is wrong myregistry.mycompany.com/olm-mirror/olm-mirror/web-terminal-web-terminal-index:v4.16
There is an extra 'olm-mirror'. In the ImageDigestMirrorSet.yaml, the path is correct, no extra 'olm-mirror' path

Thanks,
Delfim Da Costa

[ddcdk]

in mapping.txt we have also a wrong mapping :
myregistry.mycompany.com/olm-mirror/web-terminal/web-terminal-index:v4.16=myregistry.mycompany.com/olm-mirror/olm-mirror/web-terminal-web-terminal-index:v4.16
instead of :
myregistry.mycompany.com/olm-mirror/web-terminal/web-terminal-index:v4.16=myregistry.mycompany.com/olm-mirror/web-terminal-web-terminal-index:v4.16

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[ddcdk]

/remove-lifecycle stale