Bug 549278

The only suspicious issue I see in the log is:

 2009-10-22 19:35:30 <1> 192.168.1.4(3350) 
  [Pkg] PackageSystem.ycp:59 Pkg Builtin called: TargetInit
  [zypp] ZYppImpl.cc(initializeTarget):97 initTarget( /)

YaST seems to initialize the target at '/'. For the installation I would have expected '/mnt'. This initialization fails, pkg-binding log this and continues.

 2009-10-22 19:35:30 <3> 192.168.1.4(3350) 
  [Pkg] Target_Load.cc(TargetInitInternal):79 TargetInit has failed: 
                                              Rpm Exception

But the log finally ends later (19:35:56) when ProductControl.ycp executes 'inst_proposal'. The failed TargetInit (even if it was ok that YaST ignored it), might indicate low memory, maybe that's the reason for YaSTs termination.

The backtrace in YaST2/signal also does not show libzypp being involved. Maybe some YaST wizard can tell more.

when yast crasch it show me for a second the usual yast error (ycm weathever)

but it's shown on tty where after crasch i have linuxrc back that make me impossible to read such error.

if that may be interested i'm installing that on acer aspire one 1GB RAM and 160GB HD

in yast log file only errors are from libzypp. Reassigned to it's maintainers

Does this bug still occur on your machine with openSUSE 11.3?

Closing due to no response.

Reopened and reassigned reporter to myself.
Change Bug Title and changed to 11.3 - as this bug has been present since 10.3
Log Data really not required as this bug is totally reproducible via any NFS Installation.
Current Title is a bit unclear, however I am assuming a lot about a network Install.

This is totally reproducible on a NFS or any other type Installation 
***Yast logs are hence irrelevant and the bug remains***
No further input from previous reporter or myself is required until this has been tested at Suse.de

**Additional Information.**

If all the Network Installation and NFS Server bugs are ever going to be solved for once we have much to do.

Many bugs need to be solved in many many areas! This issue can only be realised if you use the GUI Tools available to every user and NOT going any-ware near a command prompt. 

The Sever which holds the complete source DVD - MUST HAVE A STATIC IP - DHCP + Zero Config is NOT acceptable here! - Statement not Question!

Once the DVD Source files are present and mounted it matters not if you use either NFS Server Mount Points or HTTP or HTTPS etc.

Lets just concentrate of a basic Network Install ALL via the GUI.

The presence of ANY NFS Server can only be found by the NFS Client IF you use the servers IP. 

NFS Server names are never present when the NFS Client tries to browse the Network! 
This has never been resolved since 10.0

Server Host names are of absolutely NO value and browsing for NFS Server names, yields a blank list of available servers - Nothing new here 

Once the above conditions are met, and you go no where near a command prompt,  USE ONLY user GUI Tools, the bugs come out.

Due to data limitations that face a huge amount of users, the ability to use the online source repository for Installation Is of very little OR No value!

Boot the New PC via the Network CD and start a normal local Network Installation and never use an automated Installation.

From here in its very simple for you at suse.de - Start the Network Install as above and you will see in front of you every nasty errors, bug fault, fall overs and Debug Information:!

Not only the Installation, but every ugly problem in Yast 11.3 and every ugly problem with both NFS Server and Client, will appear!

This will give you all the logs, error, debug output you need to solve the huge amount of bugs involved in this entire process.

If your wondering why users often give no response - Its because they are tired, had enough and have no faith that these issues will every be fixed!

Run a Bugzilla reporter for 'NORESPONSE"

Many thanks you help!

******Voters and other Interested users*****
Comments are important, if you don’t mind helping me a little to get this thing fixed...Please add what ever you would like to see or add or what ever.

QA - Please adjust to Milestone ???? and 11.4 situation - Thanks

Scott, could you please divide your points to several bug reports?

YaST is not piece of single stuff, so merging totally different things together does not help solving problems.

However, I'm not sure about validity of your points. Taking for example just the first one:

"The Sever which holds the complete source DVD - MUST HAVE A STATIC IP - DHCP +
Zero Config is NOT acceptable here! - Statement not Question!"

What is this? Do you mean that installation server having DHCP address does not work? That is obviously untrue. So what's your point?

I understand the need for several bugs but over the years you havn't been able to fix anything to do with static IP and the disastrous separation of Knetwork Manager from outside the control of Yast...
Try and do a non-automated installation and specify a static IP rather than DHCP - Good luck with that one...Also in an existing installations see how you go assigning a static IP without specifying a GW IP.

Sorry I have sent so many verbose and single bug reports since 10.2 and the calamity of 11.2 when you moved Network Manager control outside of Yast...and I am sorry to say that in the aspect of assigning ANYTHING outside of DHCP..nothing work much..Its all 100% producible..

There are also substantial problems with VPN configurations in network Manager which IFUP cannot provide and this whole subject of doing ANYTHING  but using DHCP just does not work! Words fail me and you lost me in 10.2

Well, if your problem is Network Manager, please file a bug for Network Mananager. If it is network setup in YaST, I can pass it to YaST network maintainer. If it is installation process itself, I might need to take care.

But you have to choose what you want to report.

I  offered comment regarding Network Manager to further highlight the existing problems with IFUP  as above, however I over this - This doesn't hurt me - It destroys the Open Suse brand from being functionally unable to connect to both internet and LAN under a huge amount of issues that are used where DHCP is no applicable.

Closed as NO WONTFIX for obvious reasons above