Bug 1653421
| Summary: | "systemd-nspawn -b" with systemd-enabled OS tree won't work with dbus-broker at host | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jan Pokorný [poki] <jpokorny> |
| Component: | dbus-broker | Assignee: | Tom Gundersen <tgunders> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | dh.herrmann, tgunders, yaneti |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-28 00:10:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
What version of dbus-broker are you running, and does journalctl give any relevant information. This was with
> dbus-broker-16-7.fc30.x86_64
> systemd-239-9.git9f3aed1.fc30.x86_64
on the host.
As mentioned, there was no good diagnostics beside some DBus related
clues (IIRC, not noted verbatim) with debug verbosity.
Are you using SELinux? Is the bug reproducible in permissive mode? Yes, naturally. Tried disabling DONTAUDIT but observed nothing suspicious. Am I alone with this observation? Strange, a minimal Rawhide VM works well also in that context. Will give it more troubleshooting. Sorry, this must have been something intermittent, perhaps related to the infamous hiccup with -6 and unreliably enablement and in turn something I inflicted on my when trying to solve that (perhaps mangling with nsswitch.conf might have caused that?). But would be really strange if everything but "systemd-nspawn" worked. Especially when there's not exactly a good visilibity into the cuncurrently running buses etc. or I just don't know where to look. That being said, now everything works so closing this bug, will reopen should this ever recidivate. Ok, that's good to hear. Thanks for testing and reporting regardless, really much appreciated! |
Initially discovered with "mock --rebuild" but observed also with plain "systemd-nspawn -bD /var/lib/machines/MACHINE", where MACHINE is created, e.g., per systemd-nspawn(1): # dnf -y --releasever=28 --installroot=/var/lib/machines/MACHINE \ --disablerepo='*' --enablerepo=fedora --enablerepo=updates install systemd passwd dnf fedora-release vim-minimal Respective systemd-nspawn will then exit with status of 1 and emitting: > Failed to register machine: Connection timed out > Parent died too early Only defining SYSTEMD_LOG_LEVEL=debug will provide some more insights. Looks like either dbus-broker is not a 100% replacement or there are some gaps with systemd integration (which doesn't preclude the former). I don't think that broken "mock" functionality (or more specifically, inability to run container workloads at least with OSes utilizing native dbus daemon and perhaps communicating up to host over DBus?) is a negligible issue for Fedora Rawhide (eventually F30) users.