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:
When virt-who run at "-d"(virt-who -b -d / virt-who -i -d) on terminal side, Failed to check virt-who at running mode.
Version-Release number of selected component (if applicable):
virt-who-0.14-1.el7.noarch
subscription-manager-1.15.5-1.el7.x86_64
python-rhsm-1.15.3-1.el7.x86_64
Satellite-6.1.0-RHEL-7-20150716.0
How reproducible:
Always
Steps to Reproduce:
1.Register system to Satellite
2.Run virt-who at common line on terminal side
[root@hp-z220-05 ~]# virt-who -b -d
[root@hp-z220-05 ~]# ps -ef|grep virt-who
root 18321 1 1 10:09 ? 00:00:00 /usr/bin/python /usr/share/virt-who/virtwho.py -b -d
root 18322 18321 0 10:09 ? 00:00:00 /usr/bin/python /usr/share/virt-who/virtwho.py -b -d
root 18326 18040 0 10:09 pts/0 00:00:00 grep --color=auto virt-who
3.Check virt-who's status
[root@hp-z220-05 ~]# systemctl status virt-who
● virt-who.service - Daemon for reporting virtual guest IDs to subscription-manager
Loaded: loaded (/usr/lib/systemd/system/virt-who.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2015-07-16 15:33:44 CST; 3 days ago
Process: 11931 ExecStart=/usr/bin/virt-who (code=exited, status=1/FAILURE)
Main PID: 11931 (code=exited, status=1/FAILURE)
Actual results:
Although virt-who is running, it still show virt-who is "Active: failed".
Expected results:
No matter run virt-who at command line or systemctl, it should show virt-who's status correctly.
Additional info:
systemd only tracks the service if it's started by systemd. So if virt-who is started from commandline, systemd doesn't know about it.
I don't think that the "-b" option makes much sense now, I'll remove it (together with VIRTWHO_BACKGROUND env var in /etc/sysconfig/virt-who).
*** This bug has been marked as a duplicate of bug 1247922 ***