On 9/21/18 2:37 PM, Thomas Lamprecht wrote: > [...] > > Single thing which was not working was the a full clone of a linked clone, > i.e., convert a CT to a template, create a linked clone with said template > as base (works) and then clone the linked clone (full clone), which seems > to work first - but then errors out with: > >> create full clone of mountpoint rootfs >> (commonPool:base-105-disk-0/vm-106-disk-0) >> /dev/rbd5 >> mke2fs 1.43.4 (31-Jan-2017) >> ... >> Removing image: 100% complete...done. >> TASK ERROR: clone failed: rbd error: rbd: error opening pool >> 'base-105-disk-0': (2) No such file or directory > > (CT105 is the template, CT106 is the linked clone, > > Same test worked on an current KRBD enabled code path and LVM-Thin > (just to ensure that this is something dooable in general), so there > may be something off with passing volume/disk names. >
FYI, this works again if I use $name not $volname in your $krbd_feature_disable call (with the FIXME question), as else we query the full volname, which in this case is 'base-105-disk-0/vm-106-disk-0' (105 the template, 106 the linked clone) but RBD does not knows about that one. _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
