Bug 14017 – Ändern von DHCP (Pool) Objekten geht nicht

Bug 14017 - Ändern von DHCP (Pool) Objekten geht nicht


Summary:	Ändern von DHCP (Pool) Objekten geht nicht

Status:	RESOLVED DUPLICATE of bug 26131

Product:	UCS
Classification:	Unclassified
Component:	UDM - CLI
Version:	UCS 2.2
Hardware:	All All

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-03-27 16:39 CET by Andre Fenske
Modified:	2018-04-13 13:29 CEST (History)
CC List:	2 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):
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 Andre Fenske

2009-03-27 16:39:44 CET

Ich habe versucht die Range eines DHCP-Pools zu ändern und dabei die unten stehende Fehlermeldung erhalten.

Traceback (most recent call last):
  File "/usr/share/univention-directory-manager-tools/univention-cli-server", line 231, in doit
    output = univention.admincli.admin.doit(arglist)
  File "/usr/lib/python2.4/site-packages/univention/admincli/admin.py", line 832, in doit
    object=univention.admin.objects.get(module, co, lo, position='', dn=dn, arg=arg)
  File "/usr/lib/python2.4/site-packages/univention/admin/objects.py", line 67, in get
    return module.object(co, lo, position, dn, arg=arg, superordinate=superordinate)
  File "/usr/lib/python2.4/site-packages/univention/admin/handlers/dhcp/pool.py", line 178, in __init__
    raise univention.admin.uexceptions.insufficientInformation, 'superordinate object not present'
insufficientInformation: superordinate object not present



Der verwendete Befehl hieß:

udm dhcp/pool move 
--superordinate cn=megaService,cn=dhcp,dc=univention,dc=test 
--dn cn=megaPool,cn=megaService,cn=dhcp,dc=univention,dc=test 
--set range="10.200.10.249 10.200.10.251"

Ein 
udm dhcp/pool list --superordinate cn=megaService,cn=dhcp,dc=univention,dc=test

gibt folgendes aus:

DN: cn=megaPool,cn=megaService,cn=dhcp,dc=univention,dc=test
ARG: None
  name: megaPool
  filler: None
  all_clients: None
  range: 10.200.10.250  10.200.10.252
  failover_peer: None
  dynamic_bootp_clients: None
  known_clients: None
  unknown_clients: None


Anhand dieser Ausgabe nehme ich an das die Angabe der superordinate des ersten Objekte korrekt ist.

Comment 1 Andre Fenske

2009-03-30 09:02:43 CEST

Weiterhin lassen sich DHCP-SharedSubnet-Objekte und DHCP-Pool-Objekte nicht verschieben. Das Problem dahinter scheint auf den ersten Blick das gleiche zu sein.

udm dhcp/pool move  
--dn  cn=megaPool,cn=megaService,cn=dhcp,dc=univention,dc=test 
--superordinate cn=megaService,cn=dhcp,dc=univention,dc=test 
--position cn=nagios,dc=univention,dc=test

Traceback (most recent call last):
  File "/usr/share/univention-directory-manager-tools/univention-cli-server", line 231, in doit
    output = univention.admincli.admin.doit(arglist)
  File "/usr/lib/python2.4/site-packages/univention/admincli/admin.py", line 832, in doit
    object=univention.admin.objects.get(module, co, lo, position='', dn=dn, arg=arg)
  File "/usr/lib/python2.4/site-packages/univention/admin/objects.py", line 67, in get
    return module.object(co, lo, position, dn, arg=arg, superordinate=superordinate)
  File "/usr/lib/python2.4/site-packages/univention/admin/handlers/dhcp/pool.py", line 178, in __init__
    raise univention.admin.uexceptions.insufficientInformation, 'superordinate object not present'
insufficientInformation: superordinate object not presen

Comment 2 Philipp Hahn

2011-12-12 11:23:01 CET

Das Problem der fehlenden Superordinate beim Bearbeiten tritt mit UCS-3.0 immer noch auf.

Comment 3 Alexander Kläser

2013-11-22 18:12:25 CET


*** This bug has been marked as a duplicate of bug 26131 ***