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.
Created attachment 495585[details]
vdsm log
Description of problem:
when preforming kill SIGSTOP to a qemu-kvm process and restarting vdsmd, vdsm reports the vm as up.
before vdsmd restart:
vdsClient -s 0 list table
37f9940f-2a3f-4afa-ac24-f8811fdfcc2b 16832 LIBVIRT-NFS-0-03 Up*
vmStats:
37f9940f-2a3f-4afa-ac24-f8811fdfcc2b
monitorResponse = -1
statsAge = 149.39
after vdsmd restart:
vdsClient -s 0 list table
37f9940f-2a3f-4afa-ac24-f8811fdfcc2b 16832 LIBVIRT-NFS-0-03 Up
vmStats dose not increase above 2:
37f9940f-2a3f-4afa-ac24-f8811fdfcc2b
monitorResponse = 0
statsAge = 1.10
Version-Release number of selected component (if applicable):
vdsm-4.9-60
How reproducible:
100%
Steps to Reproduce:
1.kill -19 qemu-kvm process
2.service vdsmd restart
(In reply to comment #2)
> Does the state flips back to Up* after a minute?
No, statsAge dose not increase above 2- the vm state stays Up after a minute.
Created attachment 495585 [details] vdsm log Description of problem: when preforming kill SIGSTOP to a qemu-kvm process and restarting vdsmd, vdsm reports the vm as up. before vdsmd restart: vdsClient -s 0 list table 37f9940f-2a3f-4afa-ac24-f8811fdfcc2b 16832 LIBVIRT-NFS-0-03 Up* vmStats: 37f9940f-2a3f-4afa-ac24-f8811fdfcc2b monitorResponse = -1 statsAge = 149.39 after vdsmd restart: vdsClient -s 0 list table 37f9940f-2a3f-4afa-ac24-f8811fdfcc2b 16832 LIBVIRT-NFS-0-03 Up vmStats dose not increase above 2: 37f9940f-2a3f-4afa-ac24-f8811fdfcc2b monitorResponse = 0 statsAge = 1.10 Version-Release number of selected component (if applicable): vdsm-4.9-60 How reproducible: 100% Steps to Reproduce: 1.kill -19 qemu-kvm process 2.service vdsmd restart