[bug?] For setups without "rpool" named ZFS pools destroying containers fails.

[digitalscribe]

I have 2 pools: hddpool and ssdpool and no rpool.
I have 1 container just created (debian 12) on hddpool.
Wanted it to destroy it just after creation from UI and I get:

zfs error: cannot open 'rpool': no such pool

zfs error: cannot open 'rpool': no such pool

TASK ERROR: could not activate storage 'rpool', zfs error: cannot import 'rpool': no such pool available

Seems like a trivial bug to me... expecting to always have rpool as if it's hardcoded somewhere...

 

[digitalscribe]

I can delete it with pct destroy just fine... so it's an UI bug of some sort.

 

[fabian]

please post your /etc/pve/storage.cfg ...

 

[milew]

Plese show your container config
pct config <VMID>

 

[digitalscribe]

container:

arch: amd64
cores: 2
features: nesting=1
hostname: pihole
memory: 512
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.1.1,hwaddr=BC:24:11:CB:50:EA,ip=192.168.1.42/24,type=veth
ostype: debian
rootfs: hddpool:subvol-102-disk-0,mountoptions=noatime,size=512M
searchdomain: domain.com
swap: 512
unprivileged: 1

storage.cfg:

dir: local
        path /var/lib/vz
        content iso
        shared 0

zfspool: rpool
        pool rpool
        content rootdir,images
        mountpoint /rpool
        sparse 0

lvmthin: local-lvm
        thinpool data
        vgname pve
        content rootdir,images

cifs: prox-vms
        path /mnt/pve/prox-vms
        server 192.168.1.101
        share prox-vms
        content backup
        prune-backups keep-all=1

zfspool: ssdpool
        pool ssdpool
        content rootdir,images
        mountpoint /ssdpool
        sparse 0

zfspool: hddpool
        pool hddpool
        content images,rootdir
        mountpoint /hddpool
        sparse 0

dir: prox-local
        path /hddpool/storage/_backup
        content backup,vztmpl,iso
        prune-backups keep-all=1
        shared 0

 

[digitalscribe]

though there is that rpool in storage.cfg... there's no rpool zfs pool itself... also no container/vm config refering to it what so ever... it's just the storage.cfg that remained with that entry...

 

[milew]

on your storage.cfg is entry rpool
if you do not have this storage remove on GUI or edit storage.cfg and try remove container.

 

[fabian]

the errors are from trying to activate that storage, if it doesn't exist, don't configure it

 

[digitalscribe]

well... it was configured and I just destroyed it from CLI, got rid of it anyway now
later edit: now that you've explained what happens seems quite logical... thank you!