Bug 705284 - VDSM: "Machine Destroyed" message when trying to set VM ticket
Summary: VDSM: "Machine Destroyed" message when trying to set VM ticket
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Igor Lvovsky
QA Contact: Jakub Libosvar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-17 09:29 UTC by Oded Ramraz
Modified: 2013-03-01 04:53 UTC (History)
7 users (show)

Fixed In Version: vdsm-4.9-69.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 07:18:34 UTC
Target Upstream Version:

Attachments (Terms of Use)
VDSM logs (644.64 KB, application/x-gzip)
2011-05-17 09:51 UTC, Oded Ramraz 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2011:1782 0 normal SHIPPED_LIVE new packages: vdsm 2011-12-06 11:55:51 UTC

Description Oded Ramraz 2011-05-17 09:29:23 UTC 
Description of problem:

I'm getting "Machine Destroyed" message whenever I'm trying to set VM ticket using vdsClient ( see Additional Information )



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

vdsm-4.9-65.el6.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

root@black-vdsb ~]# vdsClient -s 0 setVmTicket 00000000-0000-0001-1234-401000000003 1234 9999
        code = 0
        message = Machine destroyed
[root@black-vdsb ~]#
Comment 4 Oded Ramraz 2011-05-17 09:51:12 UTC 
Created attachment 499293 [details]
VDSM logs
Comment 5 Igor Lvovsky 2011-05-19 13:27:43 UTC 
http://gerrit.usersys.redhat.com/#change,440
Comment 8 Jakub Libosvar 2011-05-27 09:20:51 UTC 
Verified using vdsm-4.9-70.el6.x86_64
Comment 9 errata-xmlrpc 2011-12-06 07:18:34 UTC 
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/RHEA-2011-1782.html
Note You need to log in before you can comment on or make changes to this bug.