Error: Resize error: Unable to extend linked clone disk.
search cancel

Error: Resize error: Unable to extend linked clone disk.

book

Article ID: 402069

calendar_today

Updated On:

Products

VMware Integrated OpenStack

Issue/Introduction

  • Resize instance error
  • unable to resize a VM
  • Can not resize VMs located in the Availability Zone <Availability Zone>
  • Nova Compute logs will show similar to:
    nova-compute[755]: 2025-01-01 20:08:22.767 1 ERROR oslo_messaging.rpc.server [req-#######-######-####-############ ################################ ################################ - default default] Exception during message handling: nova.exception.ResizeError: Resize error: Unable to extend linked clone disk.

Environment

7.3

Cause

The compute definition for any Availability Zone by default is set to use linked clones.

Linked clones cannot be live resized.  See  VMware Integrated OpenStack 7.3 Administration Guide pg 86

Resolution

Change that Availability Zone to not use linked clones.

  1. Edit the novacompute Custom Resource
    #viocli update novacompute <compute resource having issues> 
  2. Under the vmware section for that Availability Zone add the following:
    use_linked_clone: "false"
  3. Save/Exit and compute pod will restart.
  4. Test with a new instance.  
    Note:  Existing instances will not be affected by this change.  Only new instances.

For example:

spec:
    conf:
      nova_compute:
        DEFAULT:
          default_schedule_zone: <Availability Zone>
          enabled_filters: RetryFilter, AvailabilityZoneFilter, ComputeFilter, ComputeCapabilitiesFilter,
            ImagePropertiesFilter, ServerGroupAntiAffinityFilter, ServerGroupAffinityFilter,
            PciPassthroughFilter, AggregateInstanceExtraSpecsFilter
          host: compute-################
        pci:
          passthrough_whitelist:
            type: multistring
            values:
            - '{"product_id": "*", "vendor_id": "*", "physical_network": "*"}'
        vmware:
          cluster_name: domain-################
          datastore_regex: ################
          host_ip: .VCenter:vcenter#:spec.hostname
          host_password: .VCenter:vcenter2:spec.password
          host_username: .VCenter:vcenter2:spec.username
          import_net_id: ################
          insecure: .VCenter:vcenter#:spec.insecure
          network_passthrough: true
          pbm_default_policy: vSAN Default Storage Policy
          pbm_enabled: "true"
          tenant_vdc: true
          use_linked_clone: "false"     <<<<< Add this line

Additional Information

Existing instances in that AZ will not be affected by this change. 

  1. For existing instances you can snapshot the instance in Openstack (this creates an image)
  2. Create a new instance from that image using a new flavor (size). 
    See Create a snapshot of the instance