Import OVA: working storage 'cephfs' does not support 'images' content type or is not file based.

[j3ke]

Hi,
I can't import ova with ceph.
I get the error "scsi0: import working storage 'cephfs' does not support 'images' content type or is not file based."
I use cephfs for the ova, isos etc. and cephpool for my vms/ct

Have I made a mistake or is it not possible to import via Ceph?

proxmox-ve: 8.3.0 (running kernel: 6.8.12-4-pve)
pve-manager: 8.3.0 (running version: 8.3.0/c1689ccb1065a83b)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-4
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph: 18.2.4-pve3
ceph-fuse: 18.2.4-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.0
libpve-storage-perl: 8.2.9
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.2.9-1
proxmox-backup-file-restore: 3.2.9-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.1
pve-cluster: 8.0.10
pve-container: 5.2.2
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-1
pve-ha-manager: 4.0.6
pve-i18n: 3.3.1
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.0
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1

 

[gurubert]

Have you added 'images' in the storage config forCephFS?

After importing the image you still can migrate it to the RBD pool.

Or select the target storage in the import dialog.

 

[AlterSchwede]

Hi,

I got the same error message. It seems that the source and the target storage needs to be the same and need to have 'import' enabled.
I would expect that the source storage need to have 'import' enabled and the target storage needs to have 'disk image' enabled but this combination is failing.
The problem seems to be independent from the storage type; I used SMB.

I hope it helps
Andreas

 

[fiona]

Hi,
regarding CephFS see: https://forum.proxmox.com/threads/proxmox-ve-8-3-released.157793/post-723710

 

[fiona]

Hi,

I got the same error message. It seems that the source and the target storage needs to be the same and need to have 'import' enabled.
I would expect that the source storage need to have 'import' enabled and the target storage needs to have 'disk image' enabled but this combination is failing.
The problem seems to be independent from the storage type; I used SMB.

no, having import for the target storage should not be required and the storages do not need to be the same. The Import Working Storage needs to be file-based and have content type images enabled.

Please share your /etc/pve/storage.cfg indicating the storage IDs for the source/import-working/target storages you used, as well as the exact error message.

 

[AlterSchwede]

Please find storage.cfg below.

I copied the same OVA to "SMB_Storage" and "SMB2". Import from "SMB_Storage" to "SMB_Storage" is working well, but import from "SMB2" to "SMB_Storage" is failing.

Error Message:

root@pve1:/etc/pve# cat storage.cfg
dir: local
        path /var/lib/vz
        content iso,vztmpl,images,backup
        shared 0

cifs: SMB_Storage
        path /mnt/pve/SMB_Storage
        server 192.168.98.232
        share PVE
        content rootdir,vztmpl,iso,import,backup,images,snippets
        prune-backups keep-all=1
        username abelz

esxi: Homelab
        server vmserver2.ebelz.de
        username root
        content import
        skip-cert-verification 1

cifs: SMB2
        path /mnt/pve/SMB2
        server 192.168.98.232
        share PVE2
        content import,iso
        prune-backups keep-all=1
        username abelz

 

[fiona]

Please find storage.cfg below.

I copied the same OVA to "SMB_Storage" and "SMB2". Import from "SMB_Storage" to "SMB_Storage" is working well, but import from "SMB2" to "SMB_Storage" is failing.

Error Message:
View attachment 78205

root@pve1:/etc/pve# cat storage.cfg
dir: local
        path /var/lib/vz
        content iso,vztmpl,images,backup
        shared 0

cifs: SMB_Storage
        path /mnt/pve/SMB_Storage
        server 192.168.98.232
        share PVE
        content rootdir,vztmpl,iso,import,backup,images,snippets
        prune-backups keep-all=1
        username abelz

esxi: Homelab
        server vmserver2.ebelz.de
        username root
        content import
        skip-cert-verification 1

cifs: SMB2
        path /mnt/pve/SMB2
        server 192.168.98.232
        share PVE2
        content import,iso
        prune-backups keep-all=1
        username abelz

Your screenshot shows that the Import Working Storage is SMB2, but that one does not support content type images according to the storage configuration. You can either enable the images content type for SMB2 or select SMB_Storage as the Import Working Storage

 

[AlterSchwede]

The screenshot shows that the error message is showing this. But the error message is wrong.
As you can see in the background, I have selected "SMB_Storage" as the target. This is why I have marked it in red.
It seems that the import functionality is using the source storage for destination too. The selected target seems to be ignored.

 

[fiona]

The screenshot shows that the error message is showing this. But the error message is wrong.
As you can see in the background, I have selected "SMB_Storage" as the target. This is why I have marked it in red.
It seems that the import functionality is using the source storage for destination too. The selected target seems to be ignored.

Please read everything again. What matters is the Import Working Storage here, which defaults to the source storage. That one is used to temporarily extract the images. You can change that storage too in the import dialog.

 

[AlterSchwede]

Oh sorry, I have not seen this. But why this is offered as default if it leads to a error message? Seems not to be logic for me. But anyway thanks for the help. I will test again once I am back at my test system.

 

[fiona]

Oh sorry, I have not seen this. But why this is offered as default if it leads to a error message? Seems not to be logic for me. But anyway thanks for the help. I will test again once I am back at my test system.

No worries and fair point! It surely can be improved to not select an invalid default. Feel free to open an enhancement request: https://bugzilla.proxmox.com

 

[j3ke]

Hi,
regarding CephFS see: https://forum.proxmox.com/threads/proxmox-ve-8-3-released.157793/post-723710

Hi, sorry for the late reply, I've been quite busy.
I want to import from cephfs (which is possible as described in the other post) to rbd (is called cephpool in my case), so not from cephfs to cephfs but from cephfs to rdb.

Of course you can do this manually, but it would be much nicer via the WebUI.

cat /etc/pve/storage.cfg
...

rbd: cephpool
        content rootdir,images
        krbd 0
        pool cephpool

cephfs: cephfs
        path /mnt/pve/cephfs
        content vztmpl,import,backup,iso
        fs-name cephfs

 

[fiona]

Hi, sorry for the late reply, I've been quite busy.
I want to import from cephfs (which is possible as described in the other post) to rbd (is called cephpool in my case), so not from cephfs to cephfs but from cephfs to rdb.

You can, you just need to specify a different Import Working Storage, i.e. one that is file-based and has images content type enabled (which is not allowed for CephFS).