Bug 135382 - Autoyast cannot properly pull or parse the XML config over a network transport.
Summary: Autoyast cannot properly pull or parse the XML config over a network transport.
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: AutoYaST (show other bugs)
Version: unspecified
Hardware: x86-64 SuSE Linux 10.0
: P5 - None : Blocker
Target Milestone: ---
Assignee: Uwe Gansert
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-23 19:30 UTC by Eli Stair
Modified: 2005-11-24 09:45 UTC (History)
0 users

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eli Stair 2005-11-23 19:30:05 UTC 
Problem varies depending on version (S93, S10).  When doing a PXE-booted installation, autoyast does not function properly if the autoyast XMl config is not specified in the initrd.  

Using this config:

(pxelinux config:)
LABEL suse10-TEST
  MENU LABEL TEST -- (network install) Install SuSE 9.3 from SuSE 10 from autoyast config
  KERNEL boot_images/OS/SING/suse10-install/linux
  APPEND initrd=boot_images/OS/SING/suse10-install/initrd-test ramdisk_size=131072 server=endor info=file:/info.ilm autoyast=http://adroit/~estair/autoyast.desktop.sda.SING hostname=


(info file-info.ilm:)
textmode=1
splash=verbose
nameserver=10.66.1.108
InstMode=nfs
Serverdir=/san/dept/sio/linux/os/suse/9.3/dist

(linuxrc.config:)
KernelPCMCIA:   1
UseUSBSCSI:     1
Product:        SUSE Linux
UpdateDir:      /linux/suse/x86_64-9.3
MemLoadImage:   204800
MemYaST:        92000
MemYaSTText:    64000
InstallDir:     /boot/inst-sys64
RescueImage:    /boot/rescue64
RootImage:      /boot/root-suse10
ModuleDisks:    0


With this setup the installations continues up until the bootloader, after which it fails for some unspecified reason (not running y2debug=1 at that point).  Grub IS present in the mounted image, but menu.lst is not written correctly according to the xml.

If the info file is pulled via tftp, it is transferred across correctly (packet cap shows it all), but autoyast errors saying it can't be accessed.  Ditto with NFS.

Attempting to specify the autoyast config via http with the S93 installer results in autoyast not being able to install any arch-specific RPM's.  

I'll be more than happy to attach any and all relevant configs, error/debug logs, and attempt any recommended procedurs or patched code.  This is a critical block to large-scale deployment.

/eli
Comment 1 Uwe Gansert 2005-11-24 09:45:21 UTC 
you have reported multiple different problems in one bug report. Which makes it a bit hard to track this bug. I split that bug now into two new bugs and I'll close this one.

The new bugs are:
#135445 for the bootloader thing
#135447 for the "unable to parse thing)