Bug 44165 – "This is not a valid hostname." message not updated when changing hostname

Bug 44165 - "This is not a valid hostname." message not updated when changing hostname


Summary:	"This is not a valid hostname." message not updated when changing hostname

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC - Computers
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:	UDM maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-03-30 16:20 CEST by Richard Ulmer
Modified:	2020-07-03 20:54 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.034
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:

Attachments
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 Richard Ulmer

2017-03-30 16:20:09 CEST

When creating a new (linux) computer-object with an invalid name (e.g. "Workstation 2") the "Hostname"-Field is red and views the hint "This is not a valid hostname.".

The problem is, that the warning keeps being displayed, even when I changed the name to a valid one. Nonetheless I can save, once the hostname is valid.

Comment 1 Ingo Steuwer

2020-07-03 20:54:10 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.