| Summary: | matahari services missing from chkconfig | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Dave Johnson <dajohnso> |
| Component: | matahari | Assignee: | Zane Bitter <zbitter> |
| Status: | CLOSED ERRATA | QA Contact: | IDM QE LIST <seceng-idm-qe-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.2 | CC: | astokes, matahari-maint, rbryant, syeghiay, zbitter |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
No description required.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-06 11:45:27 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 748554 | ||
Thinking about how to implement some test automation intelligence to run test variants depending on their arch I came across this web page which is making me question if matahari services for Fedora are properly configured for startup on next boot. http://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet [root@localhost ~]# ls /etc/systemd/system/*.wants/matahari* ls: cannot access /etc/systemd/system/*.wants/matahari*: No such file or directory [root@localhost ~]# ls /etc/systemd/system/*.wants /etc/systemd/system/default.target.wants: systemd-readahead-collect.service systemd-readahead-replay.service /etc/systemd/system/getty.target.wants: getty getty getty getty getty getty /etc/systemd/system/multi-user.target.wants: crond.service remote-fs.target rsyslog.service /etc/systemd/system/sysinit.target.wants: hwclock-load.service [root@localhost ~]# Fix committed to spec file in upstream repo: https://github.com/matahari/matahari/commit/8641b688e1d9a6530746d41c87fe326b202661ec good to go in v0.4.4-9
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
No description required.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1569.html |
Description of problem: ============================ Summary says it all, after installing matahari on a fresh os I noticed that none of the services are in the chkconfig --list output. They can be manually added by running 'chkconfig --add service-name'. Also, not sure if this is an additional issue but when chasing this bug, I looked at the init script and noticed that the Provides value is not filled in for any of the matahari services. ### BEGIN INIT INFO # Provides: # Required-Start: $local_fs matahari-broker Compared to libvirt-qmf which does have a value. ### BEGIN INIT INFO # Provides: libvirt-qmf # Should-Start: libvirtd This is the case on all arches Version-Release number of selected component (if applicable): ================================================================= matahari-0.4.4-8.el6.ppc64 matahari-agent-lib-0.4.4-8.el6.ppc64 matahari-broker-0.4.4-8.el6.ppc64 matahari-consoles-0.4.4-8.el6.ppc64 matahari-host-0.4.4-8.el6.ppc64 matahari-lib-0.4.4-8.el6.ppc64 matahari-network-0.4.4-8.el6.ppc64 matahari-service-0.4.4-8.el6.ppc64 matahari-sysconfig-0.4.4-8.el6.ppc64