[opensuse-autoinstall] Classes do not work in 11.1 autoyast installation
Hi, I want to use classes in my autoyast installation. With the 'autoyast' parameter I'm loading the xml-file: <?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <classes config:type="list"> <class> <class_name>default</class_name> <configuration>software.xml</configuration> </class> <class> <class_name>laptop</class_name> <configuration>partitions.xml</configuration> </class> </classes> </profile> I'm booting the client via PXE boot. I can see in the log file of the http server, that the client fetches the xml file. But in contrast the client does not even try to load the class files. I can not see an obvious error in the y2log file. With 10.3 that procedure worked that way. With 11.1 it has broken for me. Any hints are appreciated. thanks, Michael Wanitschek -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Tuesday 13 January 2009 08:56:54 mwani@fkf.mpg.de wrote:
I can see in the log file of the http server, that the client fetches the xml file. But in contrast the client does not even try to load the class files. I can not see an obvious error in the y2log file. With 10.3 that procedure worked that way. With 11.1 it has broken for me.
Any hints are appreciated.
sorry, I somehow overlooked that mail until someone pointed it out to me. Yes, classes are broken on 11.0 and 11.1 and they work only if you use at least one rule too. That rule can be very simple like "use always my.xml" or so. For 11.2 and SLES11 that's fixed -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Dear Uwe! Uwe Gansert wrote:
On Tuesday 13 January 2009 08:56:54 mwani@fkf.mpg.de wrote:
I can see in the log file of the http server, that the client fetches the xml file. But in contrast the client does not even try to load the class files. I can not see an obvious error in the y2log file. With 10.3 that procedure worked that way. With 11.1 it has broken for me.
Any hints are appreciated.
sorry, I somehow overlooked that mail until someone pointed it out to me. Yes, classes are broken on 11.0 and 11.1 and they work only if you use at least one rule too.
What exactly does this mean? Could you please explain a little bit more detailed!?
That rule can be very simple like "use always my.xml" or so.
In openSUSE 11.1 I am using rules and in one of the xml files added by a rule, I am trying the following: <classes config:type="list"> <class> <class_name>software</class_name> <configuration>all.xml</configuration> </class> </classes> But this doesn't work. all.xml is not included. My mistake or connected to this bug in openSUSE 11.1?
For 11.2 and SLES11 that's fixed
Is it possible to use this fix for openSUSE 11.1 as well? Just for the case, using profiles is not enough. Best regards, - Guenther Haas, Uni Ulm, Abteilung TAIT, guenther.haas@gmx.de
on Tuesday 11 August 2009 Guenther Haas wrote:
Yes, classes are broken on 11.0 and 11.1 and they work only if you use at least one rule too.
What exactly does this mean? Could you please explain a little bit more detailed!?
if you want to use classes, you need at least one rule in a rules.xml file too (can be a fetching all and matching always rule).
<classes config:type="list">
<class> <class_name>software</class_name> <configuration>all.xml</configuration> </class>
</classes>
so you have a classes/software/all.xml file? If you have a rule too, it should work. The bug is workarounded by using at least one rule.
But this doesn't work. all.xml is not included. My mistake or connected to this bug in openSUSE 11.1?
if you have a rule, there should be something different wrong. Maybe you can see something in the /var/log/YaST2/y2log file?
For 11.2 and SLES11 that's fixed
Is it possible to use this fix for openSUSE 11.1 as well? Just for the case, using profiles is not enough.
I did a driverupdate for 11.1 a while ago: http://www.suse.de/~ug/download/ you can try that -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Uwe Gansert wrote:
I did a driverupdate for 11.1 a while ago: http://www.suse.de/~ug/download/ you can try that
Thanks. Adding the file "diverupdate" to the root of the openSUSE installation leads to the following message:
nfs://.../RAID/install/SuSE11.1/autoyast/MEDIA/SuSE/d File not signed.
If you really trust your repository, you may continue in an insecure mode.
(OK) (BACK)
Is there anyway a way to avoid this? I already have the following section in my configuration: <signature-handling> <accept_unsigned_file config:type="boolean">true</accept_unsigned_file> <accept_file_without_checksum config:type="boolean">true</accept_file_without_checksum> <accept_verification_failed config:type="boolean">true</accept_verification_failed> <accept_unknown_gpg_key config:type="boolean">true</accept_unknown_gpg_key> <import_gpg_key config:type="boolean">true</import_gpg_key> </signature-handling> But this doesn't help. By the way: The update doesn't solve my problem. Adding the class still doesn't work. The file default.xml is included by a rule, and includes the class software/all.xml. This is not using classes recursively, which doesn't work!? Or is it? Regards, -- Guenther Haas, Uni Ulm, Abteilung TAIT, guenther.haas@gmx.de
on Tuesday 11 August 2009 Guenther Haas wrote:
Adding the file "diverupdate" to the root of the openSUSE installation
leads to the following message:
nfs://.../RAID/install/SuSE11.1/autoyast/MEDIA/SuSE/d File not signed.
Is there anyway a way to avoid this? I already have the following section in my configuration:
ah, sorry. I should add that to the README file. Add "insecure=1" to the linuxrc parameter list
By the way: The update doesn't solve my problem. Adding the class still doesn't work.
I expected that, since you have a "rule", so the bug solved by the driverupdate could not be the reason for your problem. You should really take a look at the y2log file to see if there is something going wrong. From remote it's hardly possible for me to see what's up.
The file default.xml is included by a rule, and includes the class software/all.xml.
classes/software/all.xml right? Do you use a webserver or so? can you see if autoyast tries to access all.xml in a way that fails maybe in the acces logfile? -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
I've been stumped on this one for days now and can't figure out what I'm doing wrong. I've signed the add_on_products.xml, I can point to the updates directory in the autoyast file and it works fine. The add_on_products.xml file does not add on the updates if I use that though. Here's the add_on_products.xml file: <?xml version="1.0"?> <add_on_products xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <product_items config:type="list"> <product_item> <name>sles11 updates</name> <url>nfs://devlinux.pbsg.pvt/usr/sle11/sles11/x86_64/DVD/updates</url> <path>/</path> <ask_user config:type="boolean">false</ask_user> <selected config:type="boolean">true</selected> </product_item> </product_items> </add_on_products> And here's the add-on section in the autoyast file: <add-on> <add_on_products config:type="list"> <listentry> <media_url>nfs://devlinux.pbsg.pvt/usr/sle11/sles11/x86_64/DVD/updates</media_url> <product>updates</product> <product_dir>/</product_dir> </listentry> </add_on_products> </add-on> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
on Sunday 13 September 2009 Stephens, Bill {PBSG} wrote:
I've been stumped on this one for days now and can't figure out what I'm doing wrong. I've signed the add_on_products.xml, I can point to the updates directory in the autoyast file and it works fine. The add_on_products.xml file does not add on the updates if I use that though. Here's the add_on_products.xml file:
your add_on_products.xml looks good to me and when autoyast can add the add- on, it's very likely that something with the signing went wrong and yast ingored the add_on_products.xml file. Take a look at the y2log and search for "add_on_products.xml" (or simply use autoyast instead of the add_on_products.xml ;) ) -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug listening to: "Thirteen" by Danzig -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (4)
-
Guenther Haas -
mwani＠fkf.mpg.de -
Stephens, Bill {PBSG} -
Uwe Gansert