#2823 Integration tests: Use dbus-daemon in cwrap enviroment for test
Closed: Fixed 2 years ago Opened 4 years ago by lslebodn.

Infopipe provider is not tested by downstream yet.
This ticket should cover sample test with non-system dbus-daemon in cwrap enviroment.

NOTE:
dbus-daemon can be started as ordinary user, but we also might use uid_wrapper for this. We will need to prepare a configuration file for dbus-daemon and maybe extend uid_wrapper if required.


Fields changed

blocking: => #2825

It would be nice to get at least basic test working for 1.13, because the planned status tool will read data from dbus and we will want that tested, too

Tests don't need BZ clone

rhbz: => 0

Fields changed

owner: somebody => lslebodn

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13.3
priority: major => minor

I'm sorry but we don't have time to implement this ticket in the 1.13 timeframe. Moving to 1.14 for now.

milestone: SSSD 1.13.3 => SSSD 1.14 beta

This would be a nice enhancement, so I won't push it out of 1.14 completely, but to the backlog for now.

milestone: SSSD 1.14 beta => SSSD 1.14 backlog

Since the 1.14 branch is transitioning into maintenance mode and new functionality is being developed in master which will become 1.15 eventually, I'm mass-moving tickets from the 1.14 backlog milestone to the "Future releases" milestone.

milestone: SSSD 1.14 backlog => SSSD Future releases (no date set yet)

Fields changed

milestone: SSSD Future releases (no date set yet) => SSSD Continuous integration

Metadata Update from @lslebodn:
- Issue assigned to lslebodn
- Issue marked as blocked by: #2825
- Issue set to the milestone: SSSD Continuous integration

3 years ago

Metadata Update from @lslebodn:
- Custom field blocking reset (from #2825)
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None

2 years ago

Metadata Update from @lslebodn:
- Custom field blocking adjusted to #2825
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue tagged with: PR

2 years ago

Metadata Update from @lslebodn:
- Custom field blocking reset (from #2825)
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)

2 years ago

Metadata Update from @lslebodn:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue unmarked as depending on: #2825

2 years ago

Metadata Update from @lslebodn:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue close_status updated to: Fixed
- Issue set to the milestone: SSSD 1.16.1 (was: SSSD Continuous integration)
- Issue status updated to: Closed (was: Open)

2 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/3864

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