Bugzilla – Bug 1218456
389-ds: command "dsconf <inst> repl-agmt status" issue
Last modified: 2024-01-08 23:04:17 UTC
I have two servers A and B running 389-ds with a replication agreement. On server A I run the command: dsconf <inst> repl-agmt status --suffix=<suffix> <agreement> which shows me the status of the agreement. After updating to 389-ds-2.2.8~git51.3688d68-150500.3.14.1 such command does not work anymore. After I type it, it asks: Enter bind DN for the replicated suffix (<suffix>) on <host B>:636 Enter password for (<bind DN>) to the replicated suffix (<suffix>) on <host B>:636 I can type any answer to the two previous question and the command completes and shows me the status of the agreement. In order to avoid to be prompted with the two question I can run the command as: dsconf <inst> repl-agmt status --suffix=<suffux> --bind-dn "" --bind-passwd "" <agreement> and then it works as before. I have to say that when there is a 389-ds update, there is a 20%-40% chance that something breaks in my script. I would expect such behavior in tumbleweed but not in Leap which is supposed to be quite stable.
> > I have to say that when there is a 389-ds update, there is a 20%-40% chance > that something breaks in my script. I would expect such behavior in > tumbleweed but not in Leap which is supposed to be quite stable. This was a planned and backported bug fix: https://github.com/389ds/389-ds-base/issues/5971 Upstream 389-ds prioritises fixes and working user experiences over "never changing" the CLI. This is why sometimes these things change.