Bug 35601

Summary: System setup wizard does not apply changed IP settings if dhcp was preconfigured
Product: UCS Reporter: Erik Damrose <damrose>
Component: System setupAssignee: Sönke Schwardt-Krummrich <schwardt>
Status: CLOSED FIXED QA Contact: Erik Damrose <damrose>
Severity: normal    
Priority: P5 CC: schwardt, walkenhorst
Version: UCS 3.2   
Target Milestone: UCS 3.2-3-errata   
Hardware: Other   
OS: Linux   
What kind of report is it?: --- What type of bug is this?: ---
Who will be affected by this bug?: --- How will those affected feel about the bug?: ---
User Pain: Enterprise Customer affected?:
School Customer affected?: ISV affected?:
Waiting Support: Flags outvoted (downgraded) after PO Review:
Ticket number: Bug group (optional): Usability
Max CVSS v3 score:

Description Erik Damrose univentionstaff 2014-08-12 12:26:09 CEST
univention-system-setup version 7.0.69-50
While preparing new images, i found the following error: UCS is installed with univention-system-setup-boot, the network is configured for DHCP.

When using the system setup wizard and the system receives a valid IP address from a DHCP server, it will keep this address even after system setup finishes.
 
That is, i can disable the interface DHCP option and enter a different IP address. System setup will even show me the supposed new address in the final configuration step, but the IP address is never changed.

This is confusing for users, as they expect the system to be available at the new IP address.
Comment 1 Erik Damrose univentionstaff 2014-08-12 12:44:17 CEST
The profile that is written by the wizard reads interfaces/eth0/type="dhcp", the new ip address is now present
Comment 2 Erik Damrose univentionstaff 2014-08-12 12:56:09 CEST
(In reply to Erik Damrose from comment #1)
> the new ip address is now present
That should have read _not_ instead of now
Comment 3 Sönke Schwardt-Krummrich univentionstaff 2014-08-12 15:51:44 CEST
The backend read the current interface configuration from UCR and the added the config values returned by the frontend. Given that the frontend does only specify the boolean value "ip4dynamic" if DHCP was enabled, it was impossible to switch from DHCP to static network configuration.

The frontend now always sends the boolean value "ip4dynamic" and the backend assumes "false" if the frontend did not send the value.

2014-08-12-univention-system-setup.yaml
Comment 4 Erik Damrose univentionstaff 2014-08-13 10:27:59 CEST
OK: Always apply network configuration (activated checkbox with DHCP available/unavailable, deactivated checkbox with DHCP available/unavailable)
OK: 2014-08-12-univention-system-setup.yaml

Verified
Comment 5 Sönke Schwardt-Krummrich univentionstaff 2014-08-14 11:13:43 CEST
Note: the patch has also been ported to UCS 4.0-0
Comment 6 Janek Walkenhorst univentionstaff 2014-08-14 11:54:17 CEST
http://errata.univention.de/ucs/3.2/179.html