[Bug 754649] New: Unable to install domU on Xen using autoyast with simple partition layout

https://bugzilla.novell.com/show_bug.cgi?id=754649 https://bugzilla.novell.com/show_bug.cgi?id=754649#c0 Summary: Unable to install domU on Xen using autoyast with simple partition layout Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: All OS/Version: SLES 11 Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST AssignedTo: ug@suse.com ReportedBy: nicolas.michaux@c2d.be QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=483828) --> (http://bugzilla.novell.com/attachment.cgi?id=483828) Patch to return 4 MaxPrimary partitions in Partitions.ycp User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.83 Safari/535.11 We used to install domU on Xen using autoyast with this simple partition layout : - /dev/xenvg/machine-root -> xvda1 (root) - /dev/xenvg/machine-swap -> xvda2 (swap) This has always worked fine since SLES10 until SLES11 SP1. With SLES11 SP2, it isn't working anymore, Yast stops with error "Error while configuring partitions". By comparing the logs between SLES11 SP1 and SLES11 SP2, it seems that module Partitions found 0 MaxPrimary partitions in SLES11 SP2 (it finds 4 MaxPrimary partitions with SLES11 SP1). By looking at the code, we can see that SLES11 SP1 was never returning 0 MaxPrimary partitions. The same problem seems to exist in latest trunk of autoyast in Opensuse. It is a very special partitioning scheme, as there is no real disk, only partitions, but it is very handy in virtual environment to work directly with partitions without using disk. Reproducible: Always Steps to Reproduce: 1. Configure an autoyast xml to use 2 partitions : <partitioning config:type="list"> <drive> <device>/dev/xvda</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>max</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> 2. Launch an autoyast installation of a domU in Xen environment with 2 LVM as partitions (xvda1 as root and xvda2 as swap) : disk=[ 'phy:/dev/xenvg/test-root,xvda1,w', 'phy:/dev/xenvg/test-swap,xvda2,w' ] Actual Results: Yast reports an error "Error while configuring partitions" Expected Results: Yast should format /dev/xvda1 with ext3 and use it as root and format /dev/xvda2 as swap and use it as swap. It works as expected with the patch attached. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=754649 https://bugzilla.novell.com/show_bug.cgi?id=754649#c2 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |aschnell@suse.com InfoProvider| |nicolas.michaux@c2d.be --- Comment #2 from Arvin Schnell <aschnell@suse.com> 2012-03-29 08:39:14 UTC --- Please provide the complete YaST logs, see http://en.opensuse.org/openSUSE:Bugreport_YaST. And please see what the content of /sys/block/xvda*/device/devtype is for all xvda devices available. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=754649 https://bugzilla.novell.com/show_bug.cgi?id=754649#c3 Nicolas Michaux <nicolas.michaux@c2d.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|nicolas.michaux@c2d.be | --- Comment #3 from Nicolas Michaux <nicolas.michaux@c2d.be> 2012-03-29 12:07:45 UTC --- Created an attachment (id=483917) --> (http://bugzilla.novell.com/attachment.cgi?id=483917) Complete YaST logs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=754649 https://bugzilla.novell.com/show_bug.cgi?id=754649#c4 Nicolas Michaux <nicolas.michaux@c2d.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nicolas.michaux@c2d.be --- Comment #4 from Nicolas Michaux <nicolas.michaux@c2d.be> 2012-03-29 12:10:03 UTC --- The content of /sys/block/xvda1/device/devtype and /sys/block/xvda2/device/devtype is vbd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=754649 https://bugzilla.novell.com/show_bug.cgi?id=754649#c5 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |nicolas.michaux@c2d.be --- Comment #5 from Arvin Schnell <aschnell@suse.com> 2012-04-02 14:21:18 UTC --- Thanks for the logs. We have improved the code to handle max primary better these artificial XEN disks better. But apart from that your XML for AutoYaST looks suspicious. You instruct AutoYaST to create the two partitions. But creating partitions on XEN disks is not possible. You could try to change the XML to <create config:type="boolean">false</create> and try again without your patch. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=754649 https://bugzilla.novell.com/show_bug.cgi?id=754649#c6 Nicolas Michaux <nicolas.michaux@c2d.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|nicolas.michaux@c2d.be | --- Comment #6 from Nicolas Michaux <nicolas.michaux@c2d.be> 2012-04-02 14:42:54 UTC --- Hi, I already tried with create = false without success (same error). I don't remember why I have create = true in xml, but it was necessary with some Service Pack of SLES10. The only version of SLES which doesn't work with create=true is SLES11 GA (SLES11 SP1 was working fine with this exact XML). As I said, I try to maintain an unique autoyast XML working from SLES10 GA to SLES11 SP2 (32 and 64 bits) for easy deployment. Hope it helps, Nicolas -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=754649 https://bugzilla.novell.com/show_bug.cgi?id=754649#c7 --- Comment #7 from Nicolas Michaux <nicolas.michaux@c2d.be> 2012-04-02 14:58:27 UTC --- I just tried with SLES10 SP3 and it doesn't work with create=false (Yast stops with an error on creating partition plan). I tried again with create=true and everything was working fine. As I use a very special disk layout, it seems that create=true is necessary in some case (but I don't think that it creates anything). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=754649 https://bugzilla.novell.com/show_bug.cgi?id=754649#c8 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #8 from Arvin Schnell <aschnell@suse.com> 2012-04-02 16:00:42 UTC --- Well, the behaviour with create is not comprehensible. Uwe that would be something for you. Otherwise the improved handling for max primary is added to SLE11 SP3, SLE12 and openSUSE 12.2. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=754649 https://bugzilla.novell.com/show_bug.cgi?id=754649#c9 --- Comment #9 from Bernhard Wiedemann <bwiedemann@suse.com> 2012-05-02 19:00:16 CEST --- This is an autogenerated message for OBS integration: This bug (754649) was mentioned in https://build.opensuse.org/request/show/116292 Factory / libstorage -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com