[Bug 1209725] New: autoinst.xml gen by "yast2 clone_system" mess thin pool LVM patitions?
http://bugzilla.opensuse.org/show_bug.cgi?id=1209725 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 --> http://bugzilla.opensuse.org/attachment.cgi?id=865832&action=edit 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 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209725 http://bugzilla.opensuse.org/show_bug.cgi?id=1209725#c1 --- Comment #1 from Joel Soete <Joel.Soete@skynet.be> --- Created attachment 865833 --> http://bugzilla.opensuse.org/attachment.cgi?id=865833&action=edit as gen by current yast2 clone_system (autotasy2-4.6.0-1.1) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209725 http://bugzilla.opensuse.org/show_bug.cgi?id=1209725#c2 --- Comment #2 from Joel Soete <Joel.Soete@skynet.be> --- Created attachment 865834 --> http://bugzilla.opensuse.org/attachment.cgi?id=865834&action=edit quik TIPS used to reach to clone my VM -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209725 http://bugzilla.opensuse.org/show_bug.cgi?id=1209725#c5 --- Comment #5 from Joel Soete <Joel.Soete@skynet.be> --- Created attachment 865836 --> http://bugzilla.opensuse.org/attachment.cgi?id=865836&action=edit save_y2logs resulting file Thx for reminder, -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209725 http://bugzilla.opensuse.org/show_bug.cgi?id=1209725#c6 --- Comment #6 from Joel Soete <Joel.Soete@skynet.be> --- (In reply to Stefan Hundhammer from comment #4)
You are aware that VirtualBox has its own clone functionality, so you don't even need to do a new installation, right?
Agreed but for me VM are just means to test matter before install on barebones ;) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209725 http://bugzilla.opensuse.org/show_bug.cgi?id=1209725#c18 Joel Soete <Joel.Soete@skynet.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #18 from Joel Soete <Joel.Soete@skynet.be> --- I confirm: - just save the present autoinst.xml and isolate the '<partitioning ...' hunk - manually update manually # diff /usr/share/YaST2/lib/y2storage/autoinst_profile/drive_section.rb.orig /usr/share/YaST2/lib/y2storage/autoinst_profile/drive_section.rb 388c388 < @partitions = partitions_from_collection(vg.lvm_lvs) ---
@partitions = partitions_from_collection(vg.all_lvm_lvs)
- re-run the cdm 'yast2 clone_system' to be able also isolte the new '<partitioning ...' and the diff is exactly what was missing : $ diff -Nau autoinst-part.xml.old autoinst-part.xml --- autoinst-part.xml.old 2023-03-31 17:17:03.875055463 +0000 +++ autoinst-part.xml 2023-03-31 17:16:26.509885903 +0000 @@ -38,6 +38,90 @@ <stripes t="integer">1</stripes> <stripesize t="integer">0</stripesize> </partition> + <partition t="map"> + <create t="boolean">true</create> + <filesystem t="symbol">xfs</filesystem> + <format t="boolean">false</format> + <lv_name>extra</lv_name> + <mount>/Extra</mount> + <mountby t="symbol">device</mountby> + <pool t="boolean">false</pool> + <resize t="boolean">false</resize> + <size>4294967296</size> + <stripes t="integer">1</stripes> + <stripesize t="integer">0</stripesize> + <used_pool>thin_pool00</used_pool> + </partition> + <partition t="map"> + <create t="boolean">true</create> + <filesystem t="symbol">xfs</filesystem> + <format t="boolean">false</format> + <lv_name>home</lv_name> + <mount>/home</mount> + <mountby t="symbol">device</mountby> + <pool t="boolean">false</pool> + <resize t="boolean">false</resize> + <size>4294967296</size> + <stripes t="integer">1</stripes> + <stripesize t="integer">0</stripesize> + <used_pool>thin_pool00</used_pool> + </partition> + <partition t="map"> + <create t="boolean">true</create> + <filesystem t="symbol">xfs</filesystem> + <format t="boolean">false</format> + <lv_name>opt</lv_name> + <mount>/opt</mount> + <mountby t="symbol">device</mountby> + <pool t="boolean">false</pool> + <resize t="boolean">false</resize> + <size>4294967296</size> + <stripes t="integer">1</stripes> + <stripesize t="integer">0</stripesize> + <used_pool>thin_pool00</used_pool> + </partition> + <partition t="map"> + <create t="boolean">true</create> + <filesystem t="symbol">xfs</filesystem> + <format t="boolean">false</format> + <lv_name>root</lv_name> + <mount>/</mount> + <mountby t="symbol">device</mountby> + <pool t="boolean">false</pool> + <resize t="boolean">false</resize> + <size>17179869184</size> + <stripes t="integer">1</stripes> + <stripesize t="integer">0</stripesize> + <used_pool>thin_pool00</used_pool> + </partition> + <partition t="map"> + <create t="boolean">true</create> + <filesystem t="symbol">xfs</filesystem> + <format t="boolean">false</format> + <lv_name>syslogs</lv_name> + <mount>/var/log</mount> + <mountby t="symbol">device</mountby> + <pool t="boolean">false</pool> + <resize t="boolean">false</resize> + <size>4294967296</size> + <stripes t="integer">1</stripes> + <stripesize t="integer">0</stripesize> + <used_pool>thin_pool00</used_pool> + </partition> + <partition t="map"> + <create t="boolean">true</create> + <filesystem t="symbol">xfs</filesystem> + <format t="boolean">false</format> + <lv_name>var</lv_name> + <mount>/var</mount> + <mountby t="symbol">device</mountby> + <pool t="boolean">false</pool> + <resize t="boolean">false</resize> + <size>4294967296</size> + <stripes t="integer">1</stripes> + <stripesize t="integer">0</stripesize> + <used_pool>thin_pool00</used_pool> + </partition> </partitions> <pesize>4194304</pesize> <type t="symbol">CT_LVM</type> #===<>===# Awesome job. Thx a lot for quick help, Joel -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209725 http://bugzilla.opensuse.org/show_bug.cgi?id=1209725#c19 --- Comment #19 from Joel Soete <Joel.Soete@skynet.be> --- (In reply to Ancor Gonzalez Sosa from comment #17)
Preliminary fix with regression unit test: https://github.com/yast/yast-storage-ng/pull/1327
Who is supposed to change the status report to 'RESOLVED' ? Thx a lot again, Joel -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com