Apply change from the opsman will fail with below error.
Extracting stemcell from '/var/tempest/stemcells/light-bosh-aws-xen-hvm-ubuntu-jammy-go_agent-1.682.tgz':
reading extracted stemcell manifest in '/home/tempest-web/.bosh/installations/b12rt0d8-6796-4858-8c41-888a164d4d2b/tmp/stemcell-manager8478937383':
Extracting stemcell from '/var/tempest/stemcells/light-bosh-aws-xen-hvm-ubuntu-jammy-go_agent-1.682.tgz' to '/home/tempest-web/.bosh/installation
s/b12rt0d8-6796-4858-8c41-888a164d4d2b/tmp/stemcell-manager8478937383':
Shelling out to tar: Running command: 'tar --no-same-owner -xzf /var/tempest/stemcells/light-bosh-aws-xen-hvm-ubuntu-jammy-go_agent-1.682.tgz -C / home/tempest-we b/.bosh/installations/b12rt0d8-6796-4858-8c41-888a164d4d2b/tmp/stemcell-manager8478937383
/var/tempest/stemcells/light-bosh-aws-xen-hvm-ubuntu-jammy-go_agent-1.682.tgz cannot open: No such file or directory
AWS
TKGI
If the stemcell is uploaded to opsman using the cp command, the stemcell will be extracted in the following format.
ubuntu:~$ sudo ls -ltr /var/tempest/stemcells/
tempest-web tempest-web 4566y77 Mar 31 07:20 light-bosh-stemcell-1.682-aws-xen-hvm-ubuntu-jammy-go_agent.tgz
Opsman expects the following format.
light-bosh-aws-xen-hvm-ubuntu-jammy-go_agent-1.682.tgz
There are 2 methods to upload the stemcell.
1) Import the stemcell directly from the opsman UI.
https://techdocs.broadcom.com/us/en/vmware-tanzu/standalone-components/tanzu-kubernetes-grid-integrated-edition/1-19/tkgi/upgrade-nsxt.html#:~:text=On%20the%20Stemcell%20Library%20page,Manager%20successfully%20applied%20the%20stemcell.
2) upload the stemcell using OM cli.
om -e upload-stemcell -s filename
These two methods are both capable of extracting stemcells in the correct format.