Skip to content

Maximum data volumes limit is picked from "default" version of hypervisor, for VMware #4101

@sureshanaparti

Description

@sureshanaparti

Maximum data volumes limit is picked from default version of hypervisor for VMware as the "product_version" parameter is not found in the host details.

This issue blocks #4102

ISSUE TYPE
  • Bug Report
COMPONENT NAME
Volume
CLOUDSTACK VERSION
4.13.0
CONFIGURATION
OS / ENVIRONMENT

VMware hypervisor

SUMMARY

Attach disk is failing with error "The specified VM already has the maximum number of data disks (13) attached. Please specify another VM." even thought the hypervisor version supports more than 13 disks, which is specified in the max_data_volumes_limit of hypervisor_capabilites table for that hypervisor version. The data volumes limit is being picked from "default" version of hypervisor instead of the actual version.

STEPS TO REPRODUCE
  1. Create a VM (in VMware hypervisor)
  2. Attach upto 14 data disks to the VM

EXPECTED RESULTS
The data disks limit from the actual hypervisor version has to be considered while attaching the disks
ACTUAL RESULTS
The data disks limit from the "default" hypervisor version is picked up while attaching the disks

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions