Bug 1330318
| Summary: | rpm-ostree status error: Error calling StartServiceByName for org.projectatomic.rpmostree1: Timeout was reached | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Chris Murphy <bugzilla> |
| Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 24 | CC: | awilliam, dominick.grift, dustymabe, dwalsh, lbrabec, lslebodn, lvrabec, mail, mattdm, mgrepl, plautrba, sgallagh, surajnarwade353, tflink, walters |
| Target Milestone: | --- | Keywords: | CommonBugs |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | AcceptedFreezeException https://fedoraproject.org/wiki/Common_F24_bugs#ostree-status-error | ||
| Fixed In Version: | selinux-policy-3.13.1-185.fc24 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-14 23:27:59 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1230434 | ||
Installed to a libvirt VM with Fedora-Atomic-dvd-x86_64-24-20160424.n.0.iso which pulled down tree 24.16. This needs a policy change. Proposed as a Freeze Exception for 24-beta by Fedora user walters using the blocker tracking app because: The update system doesn't start for Atomic Host. +1FE I think Dennis said something along the lines that Atomic would not ship with Beta, instead it would have it's own 2-week-y release process. Still, I guess it would make sense to push a fix for this so we can work on the composes, so +1 FE. +1 FE as we have a 1.4 build without this, tagging as CommonBugs... Discussed at the 2016-05-02 blocker review meeting: Accepted as a Freeze Exception for F24 Beta because this causes a significant problem in the Atomic images and we must push the fix stable to remedy that. The fix should be safe per selinux-policy update policies, so this is accepted as a freeze exception *** Bug 1332119 has been marked as a duplicate of this bug. *** *** Bug 1333176 has been marked as a duplicate of this bug. *** It should be fixed in selinux-policy-3.13.1-185.fc24. But I can reproduce it with -186 on rawhide -bash-4.3# rpm -q rpm-ostree selinux-policy rpm-ostree-2016.1-3.fc25.x86_64 selinux-policy-3.13.1-186.fc25.noarch Is fixed version somewhere in koji? either for f24 or rawhide Hi Lukas, Rawhide: http://koji.fedoraproject.org/koji/buildinfo?buildID=760201 F24: http://koji.fedoraproject.org/koji/buildinfo?buildID=760223 (In reply to Lukas Vrabec from comment #12) > Hi Lukas, > Thank you very much Lukas for fast response :-) > Rawhide: > http://koji.fedoraproject.org/koji/buildinfo?buildID=760201 > I tested fedora rawhide ostree with selinux policy from this koji build (selinux-policy-3.13.1-187.fc25) and it fixed bug for me. Great! Thank you for testing. I am having the same issue while doing F24 nightly image test on the cloud test day. # rpm-ostree status error: Error calling StartServiceByName for org.projectatomic.rpmostree1: Timeout was reached I am facing same issue on Fedora 24 atomic host on cloud test day. $ sudo rpm-ostree status error: Error calling StartServiceByName for org.projectatomic.rpmostree1: Timeout was reached Lukas, could you push selinux-policy-3.13.1-185.fc24 into fedora 24 testing? selinux-policy-3.13.1-185.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-0f4619cd21 selinux-policy-3.13.1-185.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: Command fails after 30 second hang. Version-Release number of selected component (if applicable): rpm-ostree-2015.11-2.fc24.x86_64 How reproducible: Always Steps to Reproduce: 1. rpm-ostree status 2. 3. Actual results: error: Error calling StartServiceByName for org.projectatomic.rpmostree1: Timeout was reached Expected results: Status Additional info: Apr 25 15:06:30 localhost.localdomain dbus[861]: [system] Activating via systemd: service name='org.projectatomic.rpmostree1' unit='rpm-ostreed.service' Apr 25 15:06:30 localhost.localdomain audit[1191]: AVC avc: denied { execute } for pid=1191 comm="(-ostreed)" name="rpm-ostreed" dev="dm-0" ino=1585 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:install_exec_t:s0 tclass=file permissive=0 Apr 25 15:06:30 localhost.localdomain audit[1191]: SYSCALL arch=c000003e syscall=59 success=no exit=-13 a0=5557d3394e20 a1=5557d334f7f0 a2=5557d33954c0 a3=5557d338bc90 items=0 ppid=1 pid=1191 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="(-ostreed)" exe="/usr/lib/systemd/systemd" subj=system_u:system_r:init_t:s0 key=(null) Apr 25 15:06:30 localhost.localdomain audit: PROCTITLE proctitle="(-ostreed)" Apr 25 15:06:30 localhost.localdomain systemd[1]: Starting RPM OSTree Manager... Apr 25 15:06:30 localhost.localdomain systemd[1191]: rpm-ostreed.service: Failed at step EXEC spawning /usr/libexec/rpm-ostreed: Permission denied Apr 25 15:06:30 localhost.localdomain systemd[1]: rpm-ostreed.service: Main process exited, code=exited, status=203/EXEC Apr 25 15:06:30 localhost.localdomain systemd[1]: Failed to start RPM OSTree Manager. Apr 25 15:06:30 localhost.localdomain systemd[1]: rpm-ostreed.service: Unit entered failed state. Apr 25 15:06:30 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=rpm-ostreed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Apr 25 15:06:30 localhost.localdomain systemd[1]: rpm-ostreed.service: Failed with result 'exit-code'. Apr 25 15:06:55 localhost.localdomain dbus[861]: [system] Failed to activate service 'org.projectatomic.rpmostree1': timed out