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 892280 - [vdsm] Can not run imported VM
Summary: [vdsm] Can not run imported VM
Keywords:
Status: CLOSED DUPLICATE of bug 883858
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.4
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Vered Volansky
QA Contact: Haim
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-06 10:02 UTC by Kiril Nesenko
Modified: 2016-05-05 04:37 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-07 13:58:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
logs (417.50 KB, application/x-gzip)
2013-01-06 10:02 UTC, Kiril Nesenko
no flags Details

Description Kiril Nesenko 2013-01-06 10:02:09 UTC
Created attachment 673306 [details]
logs

Description of problem:
Can not run imported VM

Thread-102878::DEBUG::2013-01-06 12:01:07,232::resourceManager::565::ResourceManager::(releaseResource) No one is waiting for resource 'Storage.5849b030-626e-47cb-ad90-3ce782d831b3', Clearing records.
Thread-102878::DEBUG::2013-01-06 12:01:07,232::task::957::TaskManager.Task::(_decref) Task=`c76e63c5-20e1-4a04-b7eb-0773a6641347`::ref 0 aborting False
Thread-102880::ERROR::2013-01-06 12:01:08,058::SecureXMLRPCServer::77::root::(handle_error) client ('10.35.16.40', 35935)
Traceback (most recent call last):
  File "/usr/lib64/python2.6/SocketServer.py", line 560, in process_request_thread
    self.finish_request(request, client_address)
  File "/usr/lib64/python2.6/site-packages/vdsm/SecureXMLRPCServer.py", line 68, in finish_request
    request.do_handshake()
  File "/usr/lib64/python2.6/ssl.py", line 279, in do_handshake
    self._sslobj.do_handshake()
SSLError: [Errno 1] _ssl.c:490: error:14094416:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate unknown
Thread-102882::ERROR::2013-01-06 12:01:10,099::SecureXMLRPCServer::77::root::(handle_error) client ('10.35.16.40', 60018)
Traceback (most recent call last):
  File "/usr/lib64/python2.6/SocketServer.py", line 560, in process_request_thread
    self.finish_request(request, client_address)
  File "/usr/lib64/python2.6/site-packages/vdsm/SecureXMLRPCServer.py", line 68, in finish_request
    request.do_handshake()
  File "/usr/lib64/python2.6/ssl.py", line 279, in do_handshake
    self._sslobj.do_handshake()
SSLError: [Errno 1] _ssl.c:490: error:14094416:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate unknown



Version-Release number of selected component (if applicable):
vdsm-4.10.2-3.0.el6ev.x86_64
qemu-kvm-rhev-0.12.1.2-2.348.el6.x86_64
libvirt-0.10.2-13.el6.x86_64


How reproducible:


Steps to Reproduce:
1. Import a vm and try to run it
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Haim 2013-01-06 11:37:18 UTC
Kiril, the above error is not related to the bug, it just shows that some engine tries to communicate with your hosts and they don't have the same key.
please make sure to login to this system and put host into maintenance, this will stop the errors.

the actual problem is:

Thread-102446::ERROR::2013-01-06 11:55:49,753::vm::680::vm.Vm::(_startUnderlyingVm) vmId=`8c2621cc-cea1-43b3-96ae-5d182b0a3738`::The vm start process failed
Traceback (most recent call last):
  File "/usr/share/vdsm/vm.py", line 642, in _startUnderlyingVm
    self._run()
  File "/usr/share/vdsm/libvirtvm.py", line 1410, in _run
    devices = self.buildConfDevices()
  File "/usr/share/vdsm/vm.py", line 490, in buildConfDevices
    self._normalizeVdsmImg(drv)
  File "/usr/share/vdsm/vm.py", line 403, in _normalizeVdsmImg
    drv['truesize'] = res['truesize']
KeyError: 'truesize'

Thread-102446::ERROR::2013-01-06 11:55:49,752::dispatcher::69::Storage.Dispatcher.Protect::(run) [Errno 2] No such file or directory: '/rhev/data-center/5849b030-626e-47cb-ad90
-3ce782d831b3/24f704e4-366e-4a76-aba7-80f9a7e92595/images/45a6e181-d9f6-4018-aeb0-e8af71b4eee3/29d729cd-bb36-4e53-844f-075dbcbebec3'
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/dispatcher.py", line 61, in run
    result = ctask.prepare(self.func, *args, **kwargs)
  File "/usr/share/vdsm/storage/task.py", line 1142, in prepare
    raise self.error
OSError: [Errno 2] No such file or directory:

Comment 3 Ayal Baron 2013-01-06 11:57:26 UTC
dup of bug 883858 ?

Comment 4 Vered Volansky 2013-01-07 13:00:47 UTC
Yep, looks like.

Comment 5 Ayal Baron 2013-01-07 13:58:04 UTC

*** This bug has been marked as a duplicate of bug 883858 ***


Note You need to log in before you can comment on or make changes to this bug.