Bug 31077 - kerberos/kpasswdserver still set to old master after backup2master
kerberos/kpasswdserver still set to old master after backup2master
Product: UCS
Classification: Unclassified
Component: backup2master
UCS 3.1
Other Linux
: P5 normal (vote)
: UCS 3.2
Assigned To: Felix Botner
Stefan Gohmann
: interim-1
Depends on:
  Show dependency treegraph
Reported: 2013-04-16 17:25 CEST by Arvid Requate
Modified: 2013-11-19 06:42 CET (History)
1 user (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:


Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2013-04-16 17:25:27 CEST
After backup2master in a customer UCS 3.1-1 test environment, the UCR variable kerberos/kpasswdserver was sill set to the old Master FQDN. Probably the UCR variable kerberos/kdc should be checked as well.

kerberos/adminserver seems to get fixed via the ldap_server.py listener module.
Comment 1 Moritz Muehlenhoff univentionstaff 2013-05-31 10:43:15 CEST
We will not ship a UCS 3.1-2 release; the next UCS release will be UCS 3.2.

As such, this bug is moved to the new target milestone.
Comment 2 Felix Botner univentionstaff 2013-06-14 12:45:19 CEST
Comment 3 Stefan Gohmann univentionstaff 2013-08-14 12:24:53 CEST
Changelog: OK, small adjustment: kerberos/adminserver → kerberos/kpasswdserver

Test: OK
Comment 4 Stefan Gohmann univentionstaff 2013-11-19 06:42:12 CET
UCS 3.2 has been released:

If this error occurs again, please use "Clone This Bug".