Bug 152029 - YaST: get hostname from DHCP inconsistency
Summary: YaST: get hostname from DHCP inconsistency
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 4
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Martin Vidner
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-18 10:03 UTC by Marcus Camen
Modified: 2006-02-27 20:23 UTC (History)
0 users

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

Attachments
Screenshot walkthrough (100.00 KB, application/x-tar)
2006-02-18 10:05 UTC, Marcus Camen 		Details
y2log (931.29 KB, application/x-tgz)
2006-02-18 10:11 UTC, Marcus Camen 		Details
View All 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 Marcus Camen 2006-02-18 10:03:02 UTC 
During installation I have to decide if I want a fixed host- / domainame or if both should be obtained from the DHCP server. If I deselect 'Change Hostname via DHCP' this setting is ignored if one changes the network settings during installation later on.
Comment 1 Marcus Camen 2006-02-18 10:05:50 UTC 
Created attachment 69167 [details]
Screenshot walkthrough

Notice the differnence between screenshot2.png and screenshot5.png
Comment 2 Marcus Camen 2006-02-18 10:11:06 UTC 
Created attachment 69168 [details]
y2log
Comment 3 Michael Gross 2006-02-20 12:46:59 UTC 
Did the installation work for you with ncurses in B4?
At the moment, this is oficially not supported due to the new packagemanager backend.

Does the same behaviour occurr when installing graphically?
Comment 4 Marcus Camen 2006-02-20 12:54:24 UTC 
Both (ncurses and graphical install) show the same behaviour regarding the DHCP hostname inconsistency.
Comment 5 Michael Gross 2006-02-20 14:04:19 UTC 
Martin: Please look into that.
Comment 6 Marcus Camen 2006-02-27 20:23:37 UTC 
Seems to be fixed in current Factory (Beta 5+)