Bug ID | 1209725 |
---|---|
Summary | autoinst.xml gen by "yast2 clone_system" mess thin pool LVM patitions? |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | AutoYaST |
Assignee | yast2-maintainers@suse.de |
Reporter | Joel.Soete@skynet.be |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
Created attachment 865832 [details] yast y2log file Hello, I would like to be able to easily clone my OpenSUSE Virtualbox VMs (possibly create my customized Vagrant box) thanks to autoyast. But as I always prefer to install my filesystems in this kind of LVM structure as follow: unixadmin@uts-ansible:~> sudo vgs VG #PV #LV #SN Attr VSize VFree ansiblevg00 1 9 0 wz--n- 39.00g 0 unixadmin@uts-ansible:~> sudo lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert boot ansiblevg00 -wi-ao---- 2.00g extra ansiblevg00 Vwi-aotz-- 2.00g thinpool00 3.15 home ansiblevg00 Vwi-aotz-- 2.00g thinpool00 3.18 opt ansiblevg00 Vwi-aotz-- 4.00g thinpool00 1.58 root ansiblevg00 Vwi-aotz-- 16.00g thinpool00 16.59 swap ansiblevg00 -wi-ao---- 4.00g syslogs ansiblevg00 Vwi-aotz-- 4.00g thinpool00 2.28 thinpool00 ansiblevg00 twi-aotz-- 32.93g 9.63 13.53 var ansiblevg00 Vwi-aotz-- 4.00g thinpool00 5.91 i.e. boot & swap as normal LV and all remaining FS as part of a thin_pool. All systems I build like this are working fine but when I create the autoinst.xlm file, if contains well the setup of the thin_pool LV but any ���������sub��������� volumes? According to opensuse doc (e.g. https://doc.opensuse.org/projects/autoyast/) it should works. So I check in the code source and easily find the sample xml file to test this figure also be able to manually update this autoinst.xml file to clone my VM :) I am attaching manip as a TIPS patch as well as y2log and original autoinst.xml