Univention Bugzilla – Bug 39913
No update of ucs-sso record on ip address change
Last modified: 2021-05-12 09:19:07 CEST
There is currently no mechanism which updates the ucs-sso dns record if a master or backup changes its ip address. Reexecuting 91univention-saml.inst understandably only adds the new ip address
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.
still happens with UCS 5-0 # ucs-sso, five.new, dns, five.new dn: relativeDomainName=ucs-sso,zoneName=five.new,cn=dns,dc=five,dc=new aRecord: 10.200.7.5 aRecord: 10.200.7.7 aRecord: 10.200.7.8 aRecord: 10.200.7.9 (master had 5 as ip, then 7, 8 and 9) I think everything we need for that is already there. /usr/sbin/univention-register-network-address client.umc_command('ip/change', { 'ip': configRegistry.get('interfaces/%s/address' % iface), 'oldip': configRegistry.get('interfaces/%s/fallback/address' % iface), we just need to remove "oldip" from the ucs-sso record during the ip/change