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.

Bug 688854

Summary:	force stop should move VM status to stopped in any case
Product:	Red Hat Enterprise Linux 6	Reporter:	Lubos Kocman <lkocman>
Component:	vdsm	Assignee:	Dan Kenigsberg <danken>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Dafna Ron <dron>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	abaron, bazulay, iheim, syeghiay, ykaul
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-30 08:10:33 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lubos Kocman 2011-03-18 09:07:52 UTC

Description of problem:

I had an incident yesterday, I restarted vdsm during migration. And guest stayed in kind of paused "state" and was marked red (running vms are marked green).

When I tried to start or stop guest (I'm not sure if start option was even there) I got unexpected error. And I really wasn't able to get rid of that paused state.

vdsClient -s 0 .... destroy ... returned unhandled exception as well.


These things just happens in production and we're not properly handling this.

service vdsmd restart (on all nodes) did not help.

So I rebooted hosts and restarted RHEVM service.

Something that might have make somebody really angry.

Version-Release number of selected component (if applicable):

rhevm ic104
vdsm-4.9-54.el6.x86_64

How reproducible:


Steps to Reproduce:
1. try to migrate host from node to node (there was kind of problem with migration, but this is not relevant now)
2. restart vdsmd on hosts
3. see guest in some kind of "unhandled" state
4. get rid of it without restarting any service or host
  
Actual results:

got to restart host and rhevm (not sure if rhevm was needed)

Expected results:

Stop button should stop guest in no matter state. All clusters have some kind of flush method that can help you check if deamon isn't already dead and so on ... you should really implement something like this.

Additional info: