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.
DescriptionAnatoly Litovsky
2014-11-10 06:36:13 UTC
Description of problem:
in virt-who.service:
virt-who is dependant on syslog.target , in systemd with rsyslog the dependncy shpould be be syslog.socket
http://www.freedesktop.org/wiki/Software/systemd/syslog/
Please change to syslog.socket
In fact, the whole syslog dependency should go away, virt-who on RHEL-7 has an ability to log to the journal directly so syslog is not used at all.
I'll remove the dependency completely.
Verified it on virt-who-0.11-4.el7.noarch.
Version-Release number of selected component (if applicable):
subscription-manager-1.13.9-1.el7.x86_64
python-rhsm-1.13.8-1.el7.x86_64
virt-who-0.11-4.el7.noarch
katello-headpin-1.4.3.28-1.el6sam_splice.noarch
candlepin-0.9.6.5-1.el6sam.noarch
Verified process:
1 Check the /usr/lib/systemd/system/virt-who.service, it hasn't include any syslog configure, therefore, verify it.
# cat /usr/lib/systemd/system/virt-who.service
[Unit]
Description=Daemon for reporting virtual guest IDs to subscription-manager
After=libvirtd.service network.target
[Service]
Type=simple
PIDFile=/var/run/virt-who.pid
ExecStart=/usr/bin/virt-who
EnvironmentFile=-/etc/sysconfig/virt-who
[Install]
WantedBy=multi-user.target
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.
https://rhn.redhat.com/errata/RHSA-2015-0430.html