Bug 39626 - Replace random host name with function name
Replace random host name with function name
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: System setup
UCS 4.1
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-23 15:24 CEST by Philipp Hahn
Modified: 2019-01-03 07:18 CET (History)
4 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 5: Will affect all installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.057
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Roadmap discussion (moved), Usability
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2015-10-23 15:24:06 CEST
When installing a new UCS system, the system gets a random name ucs-$RANDOM.$DNSDOMAIN.
Instead we should suggest
- "dc0"  for master
- "dcX" for backup (and slaves)
- "serverX" for member servers
- "ucsX" for base systems

The hostname should be selected for overwriting when that page is first shown, so the admin just has to type the now name if she wants to change it.

Rational:
- the random name is not nice.
- we should suggest something better than "master" and "backup", as this will break with "backup2master"
Comment 1 Philipp Hahn univentionstaff 2015-11-17 09:47:27 CET
The name in the UCS manual are inconsistent, as different instances have been used to create the screenshots, which have different names each time.
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:18:10 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

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