Bug 328003

Created attachment 174468 [details]
y2logs

Marcus, do you have an idea where could be the problem (before seeing config.xml)?

Francis, please try to fetch your final config.xml (used by YaST) the way described in bug 327839.

two problems here:

1) a strange image name: /cdrom/.i686-1  would be interesting to see
   the contents of the config.xml

2) the qemu instance doesn't have enough ram. call it with
   -m 128 for example, if it complains about too little ram use
   the tmpfs suggestion qemu print on the console

   

Actually, the image was created, so you should have the configuration saved under  /var/lib/YaST2/product-creator/images

Created attachment 174583 [details]
config.xml

Marcus -- as I mentioned QEMU has enough memory; namely, -m 256 which works more than fine with all other live images.

It doesn't have a name, I presume, because no template was imported and there's no other area (seems to me) to specify the image name.

Created attachment 174586 [details]
config.xml

Woops, attached the wrong config.xml. Correct one this time...

> It doesn't have a name, I presume, because no template was imported and there's
> no other area (seems to me) to specify the image name.

The image name could be specified in the very first entry in the first dialog - if you left it empty, it should not allow you to continue -> my fault.

Please try again without leaving the name empty.

The entry is called "Kiwi configuration" and the help text says "Enter the name of your image configuration or Import the directory with the existing one."

Thanks. I'd suggest having something like:

Kiwi configuration
----------------------------

Image Name
----------------------------

..since I think it would make it a little clearer perhaps, but more importantly it would give you the option of changing the image name (which you should be able to do, if you just want to import a template). 

Testing a build with the name now.

Yes - the version for SLES I was already writing about looks a bit different and closer to your proposal, so I expect a change also in openSUSE sooner or later.

Created attachment 174598 [details]
another config.xml

Even when I specify a name, the image it creates does not work (same reboot exception).

Out of interest, why do you have different SLE and openSUSE versions? Aren't you creating more work for yourself? ;-)

Ad comment 12:

When I try the attached config.xml (just with my RC1 repo), I get the known error, that I thought was already fixed:

Sep-25 15:13 <1> : Removing smart channel(s): kiwi1-14935   done
Sep-25 15:13 <1> : Reset RPM signature check to: True   done
Sep-25 15:13 <1> : Including pattern: default   failed
Sep-25 15:16 <3> : Couldn't create image package list   failed
Sep-25 15:16 <3> : Image installation failed   failed
Sep-25 15:16 <3> : KIWI exited with error(s)   done

I have kiwi-1.64-70.1. Marcus?


Ad comment 13: Yes, I am. The way of developing for more products in parallel is a bit complicated... :-)

I have fixed pattern download and tested right now. So if your
kiwi rpm changelog contains:
 

-------------------------------------------------------------------
Fri Sep 21 09:42:27 CEST 2007 - ms@suse.de

- pass allong $@ to init process (#327037)
- fixed remote download of pattern files (#327096)
- added updateMTAB function for all linuxrc's (#326386)

you shouldn't get that error

My kiwi is even newer, but I get the error:

* Tue Sep 25 2007 ms@suse.de
- fixed spec file architecture build requirements
- fixed missing copy call of config-cdroot.sh

* Mon Sep 24 2007 ms@suse.de
...

* Fri Sep 21 2007 ms@suse.de
- pass allong $@ to init process (#327037)
- fixed remote download of pattern files (#327096)
- added updateMTAB function for all linuxrc's (#326386)

than your pattern name is wrong, patterns are named for example
"default-10.3" not only "default"

Sep-25 16:36 <1> : Including pattern: default-10.3-145   failed

Also failed for "default-10.3". I still haven't tested default-10.3-145.i586, but that seems unlikely, as architecture is another part of pattern id, besides name.

I'm sorry I really don't understand what you are doing. I'm building images
the whole day long for SLES and SLED and 10.3 and I'm using patterns local
remotely without any problems ??? can you find your default or default-10.3
pattern within the repo-path/suse/setup/descr/... path ?

Hey Jiri, do you use a ftp URL ? if yes I think I could imagine the bug
here. The ftp source looks different than the http source list. Will check
that

found the bug, it depends on the title check. In case of ftp directory listing
we don't get a title page but that's not a fault. Additionally ftp listings
have different format than http listings

==> fixed

==> will submit a package in the next hour

Yes, that was an ftp source, sorry I forgot to attach my config.xml so you could see it earlier.

Thanks for the fix, I will test it again tomorrow.

One issue, however, is that I'm not using the FTP source at all (local yast2 and local rpm-dir repositories). Does your fix cover an issue with those as well?

That's why you were able to actually build the image :-) I don't think this fix is related to your problem with running in qemu; now when I will be able to build the image, I'll try to reproduce.

I was able to build the image on 10.2 (different source, maybe not ftp) with your config.xml and haven't any problem runnin in qemu; so let's see if 10.3 will give different result.

> found the bug, it depends on the title check. In case of ftp directory listing
> we don't get a title page but that's not a fault. Additionally ftp listings
> have different format than http listings

Still not working :-(

My kiwi package has
 - fixed ftp:// pattern requests (#328003)
changelog entry, so I guess it's the correct one.

The problem is not in pattern name, the $content variable is empty before "
check for ftp pages next..." section of KIWIPattern.pm (it never get filled from the http requests before), so the problem is not in the regexp. And yes, the repository is functional and I can see the directory with patterns in the browser (ftp://cml.suse.cz/netboot/find/openSUSE-10.3-RC1-DVD-i386-DVD1/suse/setup/descr/).


(BTW I wonder why you have hard-written paths like setup/descr and suse/setup/descr. AFAIK the directory with those metadata can be arbitrary, the path is specified by DESCRDIR variable of content file)

This is the dump of $response variable filled in line 212 of KIWIPattern.pm:

$VAR1 = bless( {
                 '_content' => '',
                 '_rc' => 200,
                 '_headers' => bless( {
                                        'client-date' => 'Wed, 26 Sep 2007 11:42:47 GMT',
                                        'content-type' => 'text/ftp-dir-listing',
                                        'content-length' => 0,
                                        'server' => 'Welcome to Pure-FTPd.',
                                        'client-request-num' => 1
                                      }, 'HTTP::Headers' ),
                 '_msg' => 'OK',
                 '_request' => bless( {
                                        '_content' => '',
                                        '_uri' => bless( do{\(my $o = 'ftp://10.20.3.1/netboot/find/openSUSE-10.3-RC1-DVD-i386-DVD1/suse/setup/descr')}, 'URI::ftp' ),
                                        '_headers' => bless( {
                                                               'user-agent' => 'libwww-perl/5.806'
                                                             }, 'HTTP::Headers' ),
                                        '_method' => 'GET'
                                      }, 'HTTP::Request' )
               }, 'HTTP::Response' );

Francis: I created image (using HTTP repository) and it worked in qemu.

Interesting, I can't really test this unless I start a local apache server (if I get time to, I will), since the internet here is too slow to grab that stuff directly. Though I guess it's more obvious now where the bug lies? Local+FTP repos?

strange it worked for me... I will check the content file now that's
a good idea

please check the attached patch, it worked for me on all types

Thanks

Created attachment 174865 [details]
kiwi-pattern.dif

package submitted

Well, your fix added the check for DESCRDIR, but the real problem was different (the path was correct, see comment 25 and 26).

I opened bug 328811 for this problem and this one will be mine and its focus is to find correct image template for Image Creator.

Francis, please try yast2-product-creator-2.15.8.1 from 

http://download.opensuse.org/repositories/home:/jsuchome/openSUSE_10.3/noarch/

It has new template and fixes also some other bugs reported recently. I'm still experimenting with the speed problem, looks like there is no good solution.

Good news: booted just great now. Thanks Jiri :-) 

One thing: might be an idea to make sure SaX2 is on the template ISO, I think.

I don't know what's missing to have X configured. I even tried to build the image from kiwi-desc-livesystem, but it is not better.

Do you have an idea what is missing in the template?

The template I created didn't have sax2, which it probably needs?

I tried adding it, but it was not enough. Also, the one from kiwi-desc-livesystem has all sax2-related packages and it is the same.

released

*** Bug 335141 has been marked as a duplicate of this bug. ***