#3325 python module configures services line in random order, breaking idempotency
Closed: wontfix 4 years ago by pbrezina. Opened 7 years ago by tibbs.

While trying to figure out why my configuration management system kept reporting that sssd.conf would change every time authconfig is run even though its arguments don't change, I realized that python3-sssdconfig will randomize the order of the "services" item in the "[sssd]" section.

Idempotency is important for configuration management systems like ansible; running a command twice should give exactly the same output as running it once. I can understand that it might not be reasonable to rewrite the items back in the original order, but the order chosen should at least be stable. I suspect that sticking "sorted()" in the right place would be quite sufficient.


I guess any fix would have to go into IPAChangeConf.merge() or .dump() in ipachangeconf.py, but that code is somewhat complicated.

Stephen said he'd hack on this but I'm not sure exactly when he plans on doing this, so for now I'm adding this to the future milestone.

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

Stephen said he'd hack on this but I'm not sure exactly when he plans on doing this, so for now I'm adding this to the future milestone.

Metadata Update from @thalman:
- Issue tagged with: Patch is welcome

4 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4357

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata