Bug 31974 – Move of dhcp host objects is not possible

Bug 31974 - Move of dhcp host objects is not possible


Summary:	Move of dhcp host objects is not possible

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UDM (Generic)
Version:	UCS 3.2
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	UCS 3.2-x
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-07-15 14:27 CEST by Felix Botner
Modified:	2018-04-13 13:29 CEST (History)
CC List:	4 users (show)

See Also:
What kind of report is it?:	Feature Request
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:	2013071521001083, 2015010521000351
Bug group (optional):	Workaround is available
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 Felix Botner

2013-07-15 14:27:09 CEST

OK, because the move operation is not configured in operations in admin/handlers/dhcp/host.py, but why?

(Ticket: 2013071521001083)

Comment 1 Tim Petersen

2015-01-06 07:44:22 CET

Reported again via 2015010521000351

Comment 2 Moritz Bunkus 2015-12-09 10:13:20 CET

Just a bump – customers are still hitting this issue and wondering about it.

http://forum.univention.de/viewtopic.php?f=48&t=4640

Comment 3 Florian Best

2016-09-24 15:08:10 CEST

Workaround: just remove the DHCP host and create it newly at the new position

Comment 4 Stefan Gohmann

2017-06-16 20:37:28 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 5 Stefan Gohmann

2017-08-08 07:10:35 CEST

This issue has been filed against UCS 3.2.

UCS 3.2 is out of maintenance and many UCS components have vastly 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 this issue. In this case please provide detailed information on how this issue is affecting you.