We were not handling the process of changing the replica type and id correctly. For one, we were not correctly handling a change to a hub/consumer, but it just happened to work by accident in most cases. In other cases you could not change the rid more than once.
Fix Description:
Changed the value checking to allow ID changes to 65535 which allowed the type/id pointers to be set correctly. Then the checking of the type & ID change combination had to be revised.
Also, removed the option to get just set the RID or type from dsconf. Only replication promotion/demotion should be touching these values.
Bug Description:
We were not handling the process of changing the replica type and id correctly. For one, we were not correctly handling a change to a hub/consumer, but it just happened to work by accident in most cases. In other cases you could not change the rid more than once.
Fix Description:
Changed the value checking to allow ID changes to 65535 which allowed the type/id pointers to be set correctly. Then the checking of the type & ID change combination had to be revised.
Also, removed the option to get just set the RID or type from dsconf. Only replication promotion/demotion should be touching these values.
relates: https://pagure.io/389-ds-base/issue/50909