Bug 35539 - Add new DC backup via LDAP directory in member mode shows "LDAP object" instead of DC backup
Add new DC backup via LDAP directory in member mode shows "LDAP object" inste...
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - LDAP directory
UCS 3.2
Other Linux
: P5 normal (vote)
: UCS 3.x
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-08-01 08:13 CEST by Stefan Gohmann
Modified: 2017-08-08 07:11 CEST (History)
0 users

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

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2014-08-01 08:13:43 CEST
From Bug #34093

(In reply to Florian Best from comment #28)
> (In reply to Dirk Wiesenthal from comment #25)
> > The new navigation warning works (almost). Why does it only get the real
> > name when the user changed the type? First object type is
> > computers/domaincontroller_backup
> TODO: well something strange happens in initial form loading...
Comment 1 Stefan Gohmann univentionstaff 2017-06-16 20:39:11 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 2 Stefan Gohmann univentionstaff 2017-08-08 07:11:02 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.