Bug 31447 – Do not assign computers to a room if no IP address has been set

Bug 31447 - Do not assign computers to a room if no IP address has been set


Summary:	Do not assign computers to a room if no IP address has been set

Status:	RESOLVED WONTFIX

Product:	UCS@school
Classification:	Unclassified
Component:	UMC - Computer room administration
Version:	UCS@school 4.1 R2
Hardware:	Other Linux

Importance:	P5 normal with 1 vote (vote)
Target Milestone:	UCS@school 4.1.x
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-05-24 10:49 CEST by Sönke Schwardt-Krummrich
Modified:	2019-02-05 21:16 CET (History)
CC List:	3 users (show)

See Also:
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):	External feedback, 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 Sönke Schwardt-Krummrich

2013-05-24 10:49:48 CEST

Currently the computer room administration allows the assignment of computers without IP address to a room. The computerroom does not display any computer without IP address.
This behaviour is confusing. The computerroom administration should decline to add computers without IP address or at least print a special warning with a listing of affected computer objects/names.

Comment 1 Michael Grandjean

2016-09-05 22:27:42 CEST

Yes, please. Still true for UCS@school 4.1 R2

Comment 2 Sönke Schwardt-Krummrich

2016-09-06 13:07:09 CEST

@Michael, Jens: did it happen in a specific support ticket?

Comment 3 Michael Grandjean

2016-09-06 14:25:22 CEST

@Sönke: yes, sorry. This one: Ticket#2016082421000649

Comment 4 Sönke Schwardt-Krummrich

2019-02-05 21:16:42 CET

This issue has been filled against UCS@school 4.1 (R2). The maintenance with bug 
and security fixes for UCS@school 4.1 (R2) has ended on 5th of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3 (or later). 
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.