Bug 1507550 - Start VM with floppy disk payload failed
Summary: Start VM with floppy disk payload failed
Keywords:
Status: CLOSED DUPLICATE of bug 1506517
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Michal Skrivanek
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-30 14:40 UTC by Israel Pinto
Modified: 2017-10-30 15:41 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-10-30 15:41:02 UTC
oVirt Team: Virt
Embargoed:
ipinto: planning_ack?
ipinto: devel_ack?
ipinto: testing_ack?

Attachments (Terms of Use)
engine_log_and_create_command (558.83 KB, application/x-xz)
2017-10-30 14:41 UTC, Israel Pinto 		no flags Details
View All

Description Israel Pinto 2017-10-30 14:40:27 UTC 
Description of problem:
Create VM with floppy payload and start it.
VM failed to start.

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.0-0.0.master.20171025204923.git6f4cbc5.el7.centos.noarch

How reproducible:
All the time

Steps to Reproduce:
1. Create vm with floppy payload via REST, See creation attached.
2. Start VM

Actual results:
VM failed to start

Expected results:
VM should run with payload.

Additional info:
error message:
2017-10-27 05:38:44,618+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-15) [] EVENT_ID: VM_DOWN_ERROR(119), VM CreateVmWithFloppyPayload is down with error. Exit message: [Errno 5] could not create floppy file: code 1, out mkfs.fat 3.0.20 (12 Jun 2013)

err mkfs.msdos: unable to create /var/run/vdsm/payload/9d6ec19c-093c-4999-bcad-5159bde6fed7.23b0db95ec4db44cd7cb8ad2523e451b.img
Comment 1 Israel Pinto 2017-10-30 14:41:10 UTC 
Created attachment 1345465 [details]
engine_log_and_create_command
Comment 3 Tomas Jelinek 2017-10-30 15:41:02 UTC 

*** This bug has been marked as a duplicate of bug 1506517 ***
Note You need to log in before you can comment on or make changes to this bug.