Bug 53094 - prepare-new-instance does not correctly set connector/listener/additionalbasenames
prepare-new-instance does not correctly set connector/listener/additionalbase...
Status: NEW
Product: UCS
Classification: Unclassified
Component: AD Connector
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2021-04-14 12:26 CEST by Felix Botner
Modified: 2021-04-14 12:27 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.057
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2021031121001091
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 Felix Botner univentionstaff 2021-04-14 12:26:32 CEST
prepare-new-instance adds the new basename to connector/listener/additionalbasenames (for the u-d-l). 

But this part seems to have problems with substrings

      echo "-- register second listener-instance"
      eval "$(univention-config-registry shell connector/listener/additionalbasenames)"
>>    echo $connector_listener_additionalbasenames | grep -q "$CONFIGBASENAME" || univention-config-registry set connector/listener/additionalbasenames="$connector_listener_addit  ionalbasenames $CONFIGBASENAME

The new configbase is not added if its a substring of an already configured base.

Please also have a look at "delete". We may have similar problems there.