Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
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 ~]#
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