Bug 28806 - backup2master sollte Hostnamen ändern können
backup2master sollte Hostnamen ändern können
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: backup2master
UCS 3.0
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-17 10:23 CEST by Janis Meybohm
Modified: 2017-08-08 07:07 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 Janis Meybohm univentionstaff 2012-10-17 10:23:01 CEST
Bei vielen Kunden heißt der DC-Master "master" und ein DC-Backup "backup". Bei einem Backup2Master heißt der neue DC-Master dann "backup" was die Kunden dazu veranlasst einen neuen DC-Backup zu installieren, diesen "master" zu nennen und erneut ein Backup2Master durchzuführen.

Ich denke hier wäre es hilfreich wenn der übernehmende DC-Backup beim backup2master den Hostnamen des DC-Master übernehmen könnte (und seinen "eigenen" als Alias).
Comment 1 Stefan Gohmann univentionstaff 2017-06-16 20:36:23 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:07:30 CEST
This issue has been filed against UCS 3.0.

UCS 3.0 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.