Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

ISO image fails to mount in vCloud Director 5.5 with the error: This media type is incorrect. Media type ISO was expected (2062449)

Symptoms

  • Attempting to mount an ISO CD or DVD image from the catalog to a virtual machine in vCloud Director 5.5 fails.
  • In the vCloud Director client, you see an error:

    This media type is incorrect. Media type ISO was expected.

  • The vcloud-container-debug log file (located in /opt/vmware/vcloud-director/logs/)contains entries similar to:

    ERROR | backend-activity-pool-59 | TaskActivity | [Activity Execution] Handle: urn:uuid:60315373-1f62-47fd-9ffb-49e92449df36, Current Phase: com.vmware.vcloud.

    backendbase.management.system.TaskActivity$ExecutePhase, ActivityExecutionState Parameter Names: [NDC, TASK_JOB_ID, activityPhaseStackList, com.vmware.activityEntityRecord.EntityId] - Unable to execute task
    'TaskModel [id=1c4adeeb-541c-4baa-a8d9-db56bff309e9, orgName=CloudOrg1, cellInstanceId=21, targetId=9bf5658c-8691-4ca9-b72e-dddadad41b98, jobId=60315373-1f62-47fd-9ffb-49e92449df36, operation=VAPP_INSERT_CD_
    FLOPPY, taskName=VAPP_INSERT_CD_FLOPPY, retriable=false, status=running, version=2' | vcd=eb8830b0-25a9-4221-94a2-3329597a040d,task=60315373-1f62-47fd-9ffb-49e92449df36 activity=urn:uuid:60315373-1f62-47fd-9
    ffb-49e92449df36
    com.vmware.vcloud.api.presentation.service.BadRequestException: This media type is incorrect. Media type ISO was expected.

    at com.vmware.ssdc.backend.services.impl.VmManagerImpl.insertMedia(VmManagerImpl.java:1427)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)

Cause

The issue occurs when you copy or move a CD/DVD ISO image between catalogs. During the move or copy operation, the logical_disk_type field is set to FLOPPY in the vCloud Director database, not CDROM as expected.

Resolution

This issue is resolved in vCloud Director 5.5.1 available at VMware Downloads. For more information, see the vCloud Director 5.5.1 Release Notes.

If you are unable to upgrade at this time, to work around this issue manually update the logical_disk table in the vCloud Director database.

To manually update the logical_disk table:

Warning: Make a full back up of your vCloud Director database before making any modifications. Follow the steps exactly to avoid possible database corruption.
  1. Log in to the vCloud Director database.
  2. To check which ISO image file in the catalog is affected, run this SQL statement:

    select distinct(ld.name) as "ISO Name", ld.logical_disk_type, mm.is_iso, opv.name as "Organization VDC", c.name as "Catalog" from logical_disk ld
    inner join managed_media mm on ld.name= mm.media_name
    inner join org_prov_vdc opv on ld.org_vdc_id=opv.id
    inner join catalog_item ci on ld.id=ci.entity_id
    inner join catalog c on ci.catalog_id=c.id
    where mm.creation_status='RESOLVED' and ld.logical_disk_type='FLOPPY' and mm.is_iso=1;

  3. To set the logical_disk_type to CDROM for the affected rows, run this SQL statement:

    update logical_disk set logical_disk_type='CDROM' where id in (
    select ld.id from logical_disk ld
    inner join managed_media mm on ld.name= mm.media_name
    inner join org_prov_vdc opv on ld.org_vdc_id=opv.id
    inner join catalog_item ci on ld.id=ci.entity_id
    inner join catalog c on ci.catalog_id=c.id
    where mm.creation_status='RESOLVED' and ld.logical_disk_type='FLOPPY' and mm.is_iso=1);

  4. To check that the logical_disk_type is now set to CDROM, run this SQL statement:

    select ld.name, ld.logical_disk_type, mm.is_iso, opv.name from logical_disk ld
    inner join managed_media mm on ld.name= mm.media_name
    inner join org_prov_vdc opv on ld.org_vdc_id=opv.id
    where mm.creation_status='RESOLVED' and ld.name='xxx-xxx-xxx';
Note: This is a temporary workaround. If you move another ISO image file in the catalog, the issue reoccurs and you need to re-apply the workaround.

Impact/Risks

Make a full back up of your vCloud Director database before making any modifications. Follow the steps in the Resolution section exactly to avoid possible database corruption.

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 4 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 4 Ratings
Actions
KB: