#2818 Investigate if Samba4 in Fedora can be used for SSSD CI
Closed: cloned-to-github a year ago by pbrezina. Opened 6 years ago by jhrozek.

Currently it's possible to only build Samba4 with the embedded Heimdal build in Fedora:

16:16 <jhrozek> Is it possile to build Samba DC on Fedora, even with custom patches?
16:16 <jhrozek> this would be for testing
16:23 <gladiac> sure
16:23 <gladiac> fedpkg clone samba
16:23 <gladiac> edit samba.spec
16:24 <gladiac> search for without_ad_dc
16:24 <gladiac> set it to 1
16:24 <gladiac> set with_mitkrb5 to 0
16:24 <gladiac> build a package

The MIT support is still a work in progress. We should investigate if we can already use the Fedora Samba4 packages for our CI. Maybe not on the same machine as the Heimdal libraries might conflict with system MIT libraries?

Fields changed

blockedby: => 2820

Fields changed

blockedby: 2820 => #2820

Tests don't need BZ clone

rhbz: => 0

Lukas will help with prepairing the COPR repo with Samba4.

owner: somebody => nkondrashov

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13.3

patches are on list

patch: 0 => 1

Tests are still under review, but should not block 1.13.3 release.

milestone: SSSD 1.13.3 => SSSD 1.13.4

This will be needed to test the by-SID memory cache planned for 1.14

milestone: SSSD 1.13.4 => SSSD 1.14 beta

WIP patches are on the list, but more work is needed.

milestone: SSSD 1.14 beta => SSSD 1.14 backlog

Fields changed

owner: nkondrashov => pcech

Test proposal: check mix providers when AD and IPA provider test become available

Internal data might be initialized differently if id_provider and auth_provider are set differently when the id_provider is either 'ad' or 'ipa', see e.g. #3234. When adding checks e.g. for the AD provider in CI this use-cases should be covered as well.

Connected to: https://fedorahosted.org/sssd/ticket/3234

Fields changed

milestone: SSSD 1.14 backlog => NEEDS_TRIAGE

Fields changed

milestone: NEEDS_TRIAGE => SSSD Continuous integration

Metadata Update from @jhrozek:
- Issue assigned to pcech
- Issue marked as depending on: #2820
- Issue marked as depending on: #2860
- Issue set to the milestone: SSSD Continuous integration

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

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 @pbrezina:
- Issue close_status updated to: cloned-to-github
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.