Bug 470421

Summary: Automated Installation will Fail if NO DHCP Services are Offered on the LAN
Product: [openSUSE] openSUSE 11.0 Reporter: Scott Couston <scott>
Component: InstallationAssignee: Steffen Winterfeldt <snwint>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Critical    
Priority: P5 - None CC: scott
Version: Final   
Target Milestone: ---   
Hardware: PC   
OS: openSUSE 11.0   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Scott Couston 2009-01-28 22:43:29 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-0.1 Firefox/3.0.5

GUI Automated Installation will fail if NO DHCP Services are Offered on the LAN. The assumption is that every installation has not only DHCP Services but also that the Internet is accessible during installation.

We cannot assume any condition and make our Installation program totally dependent on it.

We assume a great deal of conditions are present on every PC before Installation but what is so very poor is that autoconfig Installation falls over if either

DHCP Services are not available
AND/OR
Internet services are available at time of Installation
and any new or interested user who picks up openSuse and has the Installation fail will throw the CD out and may not return for years if ever and not to our Distro.


This is 100% reproducible in every instance!

Reproducible: Always

Steps to Reproduce:
1.Remove DHCP services from LAN AND/OR remove TCP/IP comms or AND/OR Internet availability.
2.Initiate either KDE/Gnome installation using defaults.
3.At some point in time the user will be given either a text or graphic with
a number of error responses.
Actual Results:  
Default installation will not complete - user dumped with a variety of text or graphical single error statements

Expected Results:  
Installation can detect PC environment and offer either questions to the user on unknown states or different states other that the 3 simple situations above. The Installation program should never ever abort or end on very simple environment situations.
Comment 1 Lukas Ocilka 2009-02-18 13:53:27 UTC 
No DHCP in AC -> mzugec
I guess this is a duplicate (Solved in 11.2)
Comment 2 Michal Zugec 2009-02-23 08:09:28 UTC 
Sorry, but I don't understand what's your problem. Of course we support both static/dhcp configuration.
What do you mean by point 3? Could you provide screenshot or text of error message?
Comment 3 Scott Couston 2009-02-23 20:37:04 UTC 
Steps to reproduce
1. Remove ALL DNS Services offered by your test Modem/Router ALL of them for your Test Isolated LAN.
2. Start a NEW NFS Install, I assume your NFS Server has a static address and configured IP's for your DNS Servers.
3. Make sure you re-boot NFS Client to remove any pre-existing information that may have been input via the text NFS Installation
3. After you start the GUI NFS Installation you will be prompted for the NFS Server IP and Exported Directory - Do That.
4. The GUI NFS will then fail as it cannot be allotted an IP or DNS Servers of its own.
You can confirm this is a DHCP time out if you escape the NFS GUI Splash screen.

Many Many LANs do NOT offer any DNS Services for good reasons and to assume they are present in every installation we do is just presumptuous folly.
Comment 4 Michal Zugec 2009-02-24 08:06:31 UTC 
Understand.
This is not about YaST, this is Linuxrc (stage before YaST starts). Reassigned to Linuxrc maintainer.
Scott, because openSUSE11.1 is out and we start working on openSUSE11.2, could you reproduce it on 11.1 (as I remember, something like this was already fixed)?

In my opinion this won't be fixed in 11.0 because it needs to replace installation media.
Also one more question. In the initial comment you wrote about dhcp servers and in comment#3 about dns servers - please make it clarify.
Comment 5 Steffen Winterfeldt 2009-02-24 09:12:08 UTC 
Scott, use 'netsetup=default'.
See also http://en.opensuse.org/Linuxrc.

*** This bug has been marked as a duplicate of bug 471731 ***
Comment 6 Scott Couston 2009-02-25 02:05:46 UTC 
I cannot see why  bug 471731 has been marked as a duplicate as it refers to opensuse 11.1 - Please re-examine
Comment 7 Steffen Winterfeldt 2009-02-25 08:46:26 UTC 
because it's the same bug

*** This bug has been marked as a duplicate of bug 471731 ***