#50622 ds_selinux_enabled may fail on suse in some cases
Closed: wontfix 4 years ago by firstyear. Opened 4 years ago by firstyear.

Issue Description

We don't check if we have the selinux python module in this command, so it may fail when we do not have it.


Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue set to the milestone: 1.4.2

4 years ago

Metadata Update from @tbordaz:
- Issue set to the milestone: None (was: 1.4.2)

4 years ago

Not yet, I need to know if it's okay to backport to 1.4.0 and 1.4.1 from @mreynolds

Not yet, I need to know if it's okay to backport to 1.4.0 and 1.4.1 from @mreynolds

Yeah of course it s fine. Typically if its not a RFE, or change in behavior, you can backport it to whatever branch you want.

@mreynolds Thanks mate. Just want to be sure you know what I'm up to! Rather have your input than surprise you with weird changes is all. I'll backport this today.

commit 6304942ba43282a463e2b29eb66a0afa3ca1f951 (HEAD -> 389-ds-base-1.4.0, origin/389-ds-base-1.4.0)
Author: William Brown <william@blackhats.net.au>
Date:   Wed Sep 25 12:19:37 2019 +1000

    Ticket 50622 - ds_selinux_enabled may crash on suse

commit aa1760272fca05f5be6f82c50baa4db5af6ace50 (HEAD -> 389-ds-base-1.4.1, origin/389-ds-base-1.4.1)
Author: William Brown <william@blackhats.net.au>
Date:   Wed Sep 25 12:19:37 2019 +1000

    Ticket 50622 - ds_selinux_enabled may crash on suse

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

4 years ago

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

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3677

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.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

3 years ago

Login to comment on this ticket.

Metadata