Bug 45299 - Adjusting network settings does not work
Adjusting network settings does not work
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: System setup
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-30 14:39 CEST by Sönke Schwardt-Krummrich
Modified: 2020-07-03 20:55 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 6: Setup Problem: Issue for the setup process
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.206
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sönke Schwardt-Krummrich univentionstaff 2017-08-30 14:39:43 CEST
During my last UCS technical training I had 3 cases where adjusting the network settings in system setup during installation from DVD did not work.

All 3 cases had the following in common:
Target was the installation of a new DC slave in KVM. On all 3 affected system, the DNS server was not set to the DC master but to the external DNS server. Therefore in system setup an error message was shown when the new system role "Domaincontroller slave" was about to be selected.

The error message was shown, because the DC master could not be detected automatically via DNS. The dialog offered to adjust the network settings which was done in all 3 cases, but it did not work:

case 1)
The IP address of the DC slave was the same as the IP address of the DC master.
When the IP address was corrected in system setup's network settings, the interface was not correctly set up: both IP addresses of DC master and DC slave were assigned to eth0 and therefore the master was still not reachable.

case 2)
The IP address of the DC slave was set to the network address (172.16.1.0/24).
When the IP address was corrected in system setup's network settings, the interface was not correctly set up: both IP addresses of network and DC slave were still assigned to eth0 and therefore the master was still not reachable, too.

case 3)
The IP address of the DNS server was set to the DC slave itself. When the IP address of the DNS server has been altered to the DC master in system setup's network settings, the /etc/resolv.conf still pointed back to the DC slave itself, with a similar result: DNS lookups via the DC master were not possible.

Workaround:
1) apply network settings in system setup
2) CTRL-ALT-F2 → fix interface eth0 and /etc/resolv.conf manually
3) switch back to system setup and continue installation of DC slave

This was extremely annoying since it was the safety fallback in case the network settings are wrong, but the offered dialog did not help.
Comment 1 Alexander Kläser univentionstaff 2017-08-30 16:04:32 CEST
*** Bug 45280 has been marked as a duplicate of this bug. ***
Comment 2 Florian Best univentionstaff 2017-08-31 12:44:21 CEST
This is probably a duplicate of Bug #45280. Let's see when that is fixed.
Comment 3 Florian Best univentionstaff 2017-11-30 10:55:43 CET
Please re-test this. It should be fixed.
Comment 4 Sönke Schwardt-Krummrich univentionstaff 2017-11-30 15:58:26 CET
JFYI: During the training I used the UCS 4.2-2 ISO image.
Comment 5 Ingo Steuwer univentionstaff 2020-07-03 20:55:43 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.