[opensuse-autoinstall] SLES11SP2 - repomd.xml.asc is required?
For my team, I manage several Linux auto-installations for RedHat & SLES. I have fairly stock autoyast.xml's that have been working quite well for a while. With SLES11SP2, I'm running into a new problem. As our add-on repository is for internal access only, we've never seen any value in signing our packages. I use the signature-handling flags to bypass the signing checks: <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> <accept_non_trusted_gpg_key config:type="boolean">true</accept_non_trusted_gpg_key> <import_gpg_key config:type="boolean">true</import_gpg_key> </signature-handling> </general> With SLES11SP2 (beta3) autoyast attempts to retrieve the repomd.xml.asc and repomd.xml.key files anyway. This throws up a blocking error dialog. Am I doing something wrong or has this behavior changed? -- Douglas Parrish Programmer Dell | PG Customer Operations -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
on Friday 19 August 2011 Douglas_Parrish@dell.com wrote:
For my team, I manage several Linux auto-installations for RedHat & SLES. I have fairly stock autoyast.xml's that have been working quite well for a while. With SLES11SP2, I'm running into a new problem.
As our add-on repository is for internal access only, we've never seen any value in signing our packages.
...
Am I doing something wrong or has this behavior changed?
I tried that with our latest beta of SP2 and it works fine here with an unsigned repo. Either there was something broken with beta3 or there must be something different in your XML file compared to SP1 installations. Autoyast (actually zypp) will try to load the *.asc files in anyway but that does not hurt. I get a 404 here too in the logs. -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, HRB 16746 (AG Nürnberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer Home: http://www.suse.de/~ug - Blog: http://suse.gansert.net listening to: "Super Space Invaders" by Eisenfunk -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Very odd, I can't seem to get past this. Could you look over my autoyast.xml file and see if it looks OK? We are using beta 4 now, but don't see any difference. It may be important that I'm getting the error while installing a "post-package". Autoyast appears to have no problem with the repository the first time around. Thanks, Doug <?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <firewall> <enable_firewall config:type="boolean">false</enable_firewall> <start_firewall config:type="boolean">false</start_firewall> </firewall> <general> <ask-list config:type="list"/> <mode> <confirm config:type="boolean">false</confirm> <final_reboot config:type="boolean">false</final_reboot> </mode> <mouse> <id>none</id> </mouse> <signature-handling> <accept_file_without_checksum config:type="boolean">true</accept_file_without_checksum> <accept_non_trusted_gpg_key config:type="boolean">true</accept_non_trusted_gpg_key> <accept_unknown_gpg_key config:type="boolean">true</accept_unknown_gpg_key> <accept_unsigned_file config:type="boolean">true</accept_unsigned_file> <accept_verification_failed config:type="boolean">true</accept_verification_failed> <import_gpg_key config:type="boolean">true</import_gpg_key> </signature-handling> </general> <keyboard> <keymap>english-us</keymap> </keyboard> <language> <language>en_US</language> <languages></languages> </language> <login_settings/> <networking> <keep_install_network config:type="boolean">true</keep_install_network> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <hostname>@HOSTNAME@</hostname> <resolv_conf_policy>auto</resolv_conf_policy> </dns> </networking> <sysconfig config:type="list"> <sysconfig_entry> <sysconfig_key>MODULES_LOADED_ON_BOOT</sysconfig_key> <sysconfig_path>/etc/sysconfig/kernel</sysconfig_path> <sysconfig_value>edd</sysconfig_value> </sysconfig_entry> </sysconfig> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <type config:type="symbol">CT_DISK</type> <use>all</use> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <partition_nr config:type="integer">1</partition_nr> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <mountby config:type="symbol">path</mountby> <size>auto</size> </partition> <partition> <create config:type="boolean">true</create> <partition_nr config:type="integer">2</partition_nr> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <size>auto</size> </partition> <partition> <create config:type="boolean">true</create> <partition_nr config:type="integer">3</partition_nr> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <mountby config:type="symbol">path</mountby> <size>max</size> </partition> </partitions> </drive> </partitioning> <runlevel> <default>3</default> </runlevel> <add-on> <add_on_products config:type="list"> <listentry> <media_url>http://tbdata/afs/osi/rpms</media_url> <product>Dell Add-ons</product> <name>tbdata</name> <product_dir>/</product_dir> </listentry> </add_on_products> </add-on> <software> <packages config:type="list"> <package>libstdc++33</package> </packages> <patterns config:type="list"> <pattern>base</pattern> <pattern>WBEM</pattern> <pattern>apparmor</pattern> <pattern>gnome</pattern> <pattern>x11</pattern> </patterns> <post-packages config:type="list"> <package>tb-runner-agent-suse11</package> </post-packages> </software> <timezone> <hwclock>UTC</hwclock> <timezone>America/Chicago</timezone> </timezone> <users config:type="list"> <user> <username>root</username> <user_password>password</user_password> <encrypted config:type="boolean">false</encrypted> <forename/> <surname/> </user> </users> <x11> <display_manager>gdm</display_manager> <window_manager>gnome</window_manager> <color_depth config:type="integer">16</color_depth> <monitor> <display> <max_hsync config:type="integer">56</max_hsync> <max_vsync config:type="integer">70</max_vsync> <min_hsync config:type="integer">31</min_hsync> <min_vsync config:type="integer">50</min_vsync> </display> <monitor_device>1024X768@70HZ</monitor_device> <monitor_vendor>--> VESA</monitor_vendor> </monitor> <resolution>1024x768 (XGA)</resolution> </x11> <scripts> <pre-scripts config:type="list"> <script> <interpreter>shell</interpreter> <source><![CDATA[ #!/bin/bash STAG=$(dmidecode -s system-serial-number) if [ "$STAG" != "" ] then sed "s/@HOSTNAME@/${STAG}/" /tmp/profile/autoinst.xml > /tmp/profile/modified.xml else sed "s/@HOSTNAME@/linux/" /tmp/profile/autoinst.xml > /tmp/profile/modified.xml fi ]]> </source> </script> </pre-scripts> </scripts> </profile> -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Monday, August 22, 2011 3:11 AM To: opensuse-autoinstall@opensuse.org Subject: Re: [opensuse-autoinstall] SLES11SP2 - repomd.xml.asc is required? on Friday 19 August 2011 Douglas_Parrish@dell.com wrote:
For my team, I manage several Linux auto-installations for RedHat & SLES. I have fairly stock autoyast.xml's that have been working quite well for a while. With SLES11SP2, I'm running into a new problem.
As our add-on repository is for internal access only, we've never seen any value in signing our packages.
...
Am I doing something wrong or has this behavior changed?
I tried that with our latest beta of SP2 and it works fine here with an unsigned repo. Either there was something broken with beta3 or there must be something different in your XML file compared to SP1 installations. Autoyast (actually zypp) will try to load the *.asc files in anyway but that does not hurt. I get a 404 here too in the logs. -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, HRB 16746 (AG Nürnberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer Home: http://www.suse.de/~ug - Blog: http://suse.gansert.net listening to: "Super Space Invaders" by Eisenfunk -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
on Monday 22 August 2011 Douglas_Parrish@dell.com wrote:
It may be important that I'm getting the error while installing a "post-package". Autoyast appears to have no problem with the repository the first time around.
indeed, in the 2nd stage I see that error too. I talked to the zypp guys and we'll fix that hopefully for the next beta. Thanks for the report. -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, HRB 16746 (AG Nürnberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer Home: http://www.suse.de/~ug - Blog: http://suse.gansert.net listening to: "Alice (Der Spiegeltanz)" by Stillste Stund -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Given SLES11 SP1 Task Creating an autoinstall.xml with a remove-packages section. Problem: In case a ... <remove-packages config:type="list"> </remove-packages> ... Section exist around 1000 packages MORE will be installed on an "minimal" installation. It does not matter if the section is empty or has a few entries. Solution: (for me) Remove the section completely from the xml file. Cheers Hajo -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
on Friday 09 September 2011 Hans-Joachim Ehlers wrote:
In case a ... <remove-packages config:type="list"> </remove-packages> ...
Section exist around 1000 packages MORE will be installed on an "minimal" installation.
It does not matter if the section is empty or has a few entries.
I can not reproduce that behaviour here. An empty <remove-packages> list installs the same size of packages like no <remove-packages> section at all. I only checked the proposal screen though. Do you see the misbehaviour already in the proposal screen? If yes, then there must be something special on your side that triggers it. -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, HRB 16746 (AG Nürnberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer Home: http://www.suse.de/~ug - Blog: http://suse.gansert.net listening to: "Viktor (Von Rosen Und Nekrosen)" by Stillste Stund -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (3)
-
Douglas_Parrish@Dell.com
-
Hans-Joachim Ehlers
-
Uwe Gansert