http://bugzilla.opensuse.org/show_bug.cgi?id=1010060 http://bugzilla.opensuse.org/show_bug.cgi?id=1010060#c1 --- Comment #1 from Stefan Hundhammer --- Upon investigation it turned out that the 'content' file on that ISO appears to be the problem: This distro is not properly detected as a SLES-like SUSE distro. [shundhammer @ morgul] ~ 1 % head -n 20 /mnt/content CONTENTSTYLE 11 DATADIR suse DESCRDIR suse/setup/descr DISTRO cpe:/o:suse:casp:1.0,SUSE Containers as a Service Platform 1.0 LINGUAS en_US REPOID obsproduct://build.suse.de/Devel:CASP:1.0/CASP/1.0/DVD/x86_64 VENDOR SUSE META SHA256 57c4467ce18bb3b842c7c638392ea1a26c534c6ce00eeb97b222c9b92e73b3d1 appdata.xml.gz META SHA256 ab538a0eeeb2ee6ae1bdcd0dee64d699485860315b03e3c0481847a1f2cae8a7 packages.DU.gz ... Compared with a 'content' file from a SLE-12 SP2: [shundhammer @ morgul] ~ 1 % head -n 20 /mnt2/content CONTENTSTYLE 11 DATADIR suse DESCRDIR suse/setup/descr DISTRO cpe:/o:suse:sles:12:sp2,SUSE Linux Enterprise Server 12 SP2 LINGUAS cs da de en en_GB en_US es fi fr hu it ja nb nl pl pt pt_BR ru sv zh zh_CN zh_TW REGISTERPRODUCT true REPOID obsproduct://build.suse.de/SUSE:SLE-12-SP2:GA/SLES/12.2/DVD/x86_64 VENDOR SUSE META SHA256 2213a47eb194729bc965dabb6ea18c44b4b29a0f77c478afc384ab0d7e8907eb appdata-icons.tar.gz META SHA256 776a6a747a829134046ba813e675f0059c7883f3f022d483e4d1db849e5f4698 appdata-screenshots.tar or openSUSE 13.2: [shundhammer @ morgul] ~ 1 % head -n 20 /mnt3/content CONTENTSTYLE 11 DATADIR suse DESCRDIR suse/setup/descr DISTRO cpe:/o:opensuse:opensuse:13.2,openSUSE LINGUAS cs da de en en_GB en_US es fi fr hu it ja nb nl pl pt pt_BR ru sv zh zh_CN zh_TW REPOID obsproduct://build.opensuse.org/openSUSE:13.2/openSUSE/13.2/dvd/x86_64 VENDOR openSUSE META SHA256 b7fed1e3a0b05aa46fd344cc065a08a820dbe4520dda43b500e6886abb4e7dae app-icons.tar.gz META SHA256 8c848c4086b39e36f03c1d69fdaf7038d23120734a4372de4c2383c3887795ee appdata.xml.gz Explicitly specifying --os-variant=sles12sp2 on the command line did not help at all. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1010060 http://bugzilla.opensuse.org/show_bug.cgi?id=1010060#c3 --- Comment #3 from Stefan Hundhammer --- Created attachment 701877 --> http://bugzilla.opensuse.org/attachment.cgi?id=701877&action=edit Patch to detect CASP distros -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1010060 http://bugzilla.opensuse.org/show_bug.cgi?id=1010060#c4 --- Comment #4 from Stefan Hundhammer --- I was unsure what distro to report this bug against; it's there in SLE-12 (all versions), Leap (all versions) and Tumbleweed/Factory; but since most developers probably use Tumbleweed, I decided for that. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1010060 Stefan Hundhammer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snwint@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1010060 http://bugzilla.opensuse.org/show_bug.cgi?id=1010060#c6 Charles Arnold changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|virt-bugs@suse.de |carnold@suse.com --- Comment #6 from Charles Arnold --- (In reply to Thorsten Kukuk from comment #5)

Be aware of that CASP will most likely not the final name.

It is unfortunate that SUSE doesn't have a standard format for the content file. I don't mind taking this patch - unless of course the content file changes and we need to parse the file in a different way. Perhaps we need to wait until we are closer to the release of this product so we know the content file won't change on the ISO? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1010060 http://bugzilla.opensuse.org/show_bug.cgi?id=1010060#c8 --- Comment #8 from Charles Arnold --- (In reply to Thorsten Kukuk from comment #7)

(In reply to Charles Arnold from comment #6)

...

It is unfortunate that SUSE doesn't have a standard format for the content file.

What do you mean by that? If I look at the three examples, we have a standard format for the content file. That the product names for different products differ shouldn't surprise anybody. Or what do you expect here?

virt-install has to handle versions going way back. os11.x differs from os12.x which differs from os13.x. The same also for sles10 vs sles11 which differ from their openSUSE counter parts. And of course sles12 differs from sles11. Over the years, the names of the labels have changed in the content files that point to the product description and version over all these different releases. Leap and sles12 seem to have finally settled down to something common. If CASP is following the sles12 format that is great because it will be much easier to support. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1010060 http://bugzilla.opensuse.org/show_bug.cgi?id=1010060#c10 --- Comment #10 from Stefan Hundhammer --- I just talked to Steffen Winterfeldt who has been working on linuxrc for ages (so he should know about those installation images): The relevant part of that file are the lines with the kernel and the initrd: HASH SHA256 335d14...7fc8b0670a2aee2142fa2940 boot/x86_64/loader/linux HASH SHA256 20a1c9...2ee9ced0bd01f7f6e716b162 boot/x86_64/loader/initrd As far as I saw, the ultimate goal of that distro detection is to figure out where to find the kernel and the initrd. Steffen says that as far back as he can remember it's always been like this: They have been in boot/$ARCH/.../linux and boot/$ARCH/.../initrd (that "loader" level may or may not be there), so it would be a matter of a straightforward regexp to match for that - and get the definite full path of either. The checksum (and the checksum format) can safely be ignored since this is something linuxrc checks anyway (Steffen, is this correct?). This would make all that detection for the SUSE case considerably easier, more reliable and - most importantly - future proof for products to come. How about that? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1010060 http://bugzilla.opensuse.org/show_bug.cgi?id=1010060#c12 --- Comment #12 from Charles Arnold --- One more bit of data to understand. virt-install looks at the installation source (ISO or network location) to determine what it is. It then takes that information and looks up what it found in the libosinfo database (a separate RPM). This database contains information like where the kernel and initrd are located (among other things). We can fake out the lookup for now by telling it that the ISO media we found is just a SLES12 SP2 image but eventually we will want something more specific and accurate. This means both virt-install and libosinfo will need to be fixed so when a customer points at the CASP media they see exactly what it is they are installing. -- You are receiving this mail because: You are on the CC list for the bug.