Bug 135447

Summary: Autoyast cannot properly parse the XML config over a network transport
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Uwe Gansert <ug>
Component: AutoYaSTAssignee: Uwe Gansert <ug>
Status: RESOLVED WORKSFORME QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Filtered Ethereal capture (pcap) of tftp transaction requesting autoyast config.
autoyast config used.

Description Uwe Gansert 2005-11-24 09:19:03 UTC 
This is part of a bug-split. Original bug was #135382

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


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.
Comment 1 Uwe Gansert 2005-11-24 09:45:01 UTC 
please attach the autoyast profile you use and the y2log file
Comment 2 Uwe Gansert 2005-11-30 10:06:25 UTC 
please provide the information or I'll close the bug since it works fine for me
Comment 3 Eli Stair 2005-11-30 17:47:52 UTC 
Created attachment 59286 [details]
Filtered Ethereal capture (pcap) of tftp transaction requesting autoyast config.
Comment 4 Eli Stair 2005-11-30 17:49:05 UTC 
Created attachment 59287 [details]
autoyast config used.
Comment 5 Uwe Gansert 2005-12-01 09:30:26 UTC 
I need the y2log file.
It's in /var/log/YaST2/y2log
Comment 6 Uwe Gansert 2005-12-19 14:21:05 UTC 
can't fix without info