Fields changed

owner: somebody => jhrozek

Fields changed

milestone: SSSD 1.0 => Iteration 6

Fixed in: d0682cb

fixedin: => 0.5.0
resolution: => fixed
status: new => closed

Sorry, but this is not what Jenny meant, this bug is really about bad error message. Reopening.

The thing is, that sysdb transaction can error out with ENOENT in two cases:
- the user does not exist - for example sss_usermod -c "Non-Existing User" nosuchuser
- attempting to add a valid user into or remove from a nonexistent group - for example sss_usermod -a nosuchgroup validuser

I guess there are two ways to fix it:
- the easy way, just modify the error message on ENOENT to say something like "Check user and/or groupnames given on the command line"
- the slightly harder way, if adding to or removing from groups, check if they exist first

resolution: fixed =>
status: closed => reopened

Fields changed

milestone: SSSD 0.5.0 => SSSD 0.6.0

Fields changed

doc: => 0
docupdated: => 0
milestone: SSSD 0.6.0 => SSSD 1.0
tests: => 0
testsupdated: => 0

Fixed in 62aa4da

fixedin: 0.5.0 => 0.7.0
resolution: => fixed
status: reopened => closed
tests: 0 => 1

Fields changed

tests: 1 => 0
testsupdated: 0 => 1

Fields changed

rhbz: => 0

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/1142

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.