search

hashicorp / terraform-provider-vsphere

Terraform Provider for VMware vSphere
https://registry.terraform.io/providers/hashicorp/vsphere/
Mozilla Public License 2.0
615 stars 449 forks source link

VM creation fails when reconfiguring disk post-clone #1658

Closed slavina-rumenova closed 2 years ago

slavina-rumenova commented 2 years ago

Community Guidelines

Terraform

1.1.9

Terraform Provider

2.1.1

VMware vSphere

7.0.2

Description

VM creation fails due to missing permissions on queryAssociatedProfile when triggered by an vsphere admin user:

Error: error reconfiguring virtual machine: error processing disk changes post-clone: disk.0: ServerFaultCode: NoPermission: RESOURCE (vm-41690:2000), ACTION (queryAssociatedProfile): RESOURCE (vm-41690), ACTION (PolicyIDByVirtualDisk)

I found a couple of github issues, referring to the same error message, which suggested that one requires StorageProfile.View & StorageProfile.Update permissions. My user does, however have those permission, as well as administrator privileges on the vsphere cluster. In addition, there are no Storage Profiles configured, just the default one is used. Does anyone have an idea on why this is still failing?

Affected Resources

resource/vsphere_virtual_machine

Terraform Configuration

data "vsphere_datacenter" "dc" {
  name = var.datacentername
}
data "vsphere_resource_pool" "pool" {
  name          = var.resourcepool
  datacenter_id = data.vsphere_datacenter.dc.id
}
data "vsphere_datastore" "datastore" {
  name          = var.datastore_name
  datacenter_id = data.vsphere_datacenter.dc.id
}
data "vsphere_network" "network" {
  name          = var.network
  datacenter_id = data.vsphere_datacenter.dc.id
}
data "vsphere_virtual_machine" "template" {
  name          = var.template_name
  datacenter_id = data.vsphere_datacenter.dc.id
}
resource "vsphere_virtual_machine" "app-server" {
  name             = var.vm_name
  num_cpus         = var.cpu_num
  memory           = var.memory
  datastore_id     = data.vsphere_datastore.datastore.id
  resource_pool_id = data.vsphere_resource_pool.pool.id
  guest_id         = data.vsphere_virtual_machine.template.guest_id
  scsi_type        = data.vsphere_virtual_machine.template.scsi_type
  network_interface {
    network_id = data.vsphere_network.network.id
  }
  disk {
    label = "${var.vm_name}.vmdk"
    size = var.disk_size
  }
  clone {
    template_uuid = data.vsphere_virtual_machine.template.id
    customize {
      linux_options {
        host_name = var.vm_name
        domain    = "example.com"
      }
      network_interface {
        ipv4_address    = var.ip_address
        ipv4_netmask    = var.ip_netmask
      }
      dns_server_list = var.dns_server_list
      ipv4_gateway = var.ip_gateway
    }
  }
  connection {
      type     = "ssh"
      user     = var.vm_username
      password = var.vm_password
      host     = vsphere_virtual_machine.app-server.default_ip_address 
  }
  provisioner "local-exec" {
    command = "generate-host-certs.sh ${self.name}"
  }
}

Debug Output

2022-04-29T13:48:31.432+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] Virtual machine "/SOMEDC/vm/app-server-test": clone complete (MOID: "vm-41690"): timestamp=2022-04-29T13:48:31.432+0200
2022-04-29T13:48:31.531+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] Locating resource pool with ID resgroup-1922: timestamp=2022-04-29T13:48:31.531+0200
2022-04-29T13:48:31.636+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] Resource pool found: resgroup-1922: timestamp=2022-04-29T13:48:31.636+0200
2022-04-29T13:48:31.636+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] Fetching properties for VM "//SOMEDC/vm/app-server-test": timestamp=2022-04-29T13:48:31.636+0200
2022-04-29T13:48:31.836+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] VM "//SOMEDC/vm/app-server-test" - UUID is "421571f1-f9cd-870d-c116-8eda19ad3b84": timestamp=2022-04-29T13:48:31.836+0200
2022-04-29T13:48:31.836+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] vsphere_virtual_machine (ID = 421571f1-f9cd-870d-c116-8eda19ad3b84): Building config spec: timestamp=2022-04-29T13:48:31.836+0200
2022-04-29T13:48:31.836+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] vsphere_virtual_machine (ID = 421571f1-f9cd-870d-c116-8eda19ad3b84): Resource argument "guest_id" requires a VM restart: timestamp=2022-04-29T13:48:31.836+0200
2022-04-29T13:48:31.836+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] vsphere_virtual_machine (ID = 421571f1-f9cd-870d-c116-8eda19ad3b84): Resource argument "tools_upgrade_policy" requires a VM restart: timestamp=2022-04-29T13:48:31.836+0200
2022-04-29T13:48:31.836+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] vsphere_virtual_machine (ID = 421571f1-f9cd-870d-c116-8eda19ad3b84): Resource argument "hv_mode" requires a VM restart: timestamp=2022-04-29T13:48:31.836+0200
2022-04-29T13:48:31.836+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] vsphere_virtual_machine (ID = 421571f1-f9cd-870d-c116-8eda19ad3b84): Resource argument "ept_rvi_mode" requires a VM restart: timestamp=2022-04-29T13:48:31.836+0200
2022-04-29T13:48:31.836+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] vsphere_virtual_machine (ID = 421571f1-f9cd-870d-c116-8eda19ad3b84): CPU operation requires a VM restart: timestamp=2022-04-29T13:48:31.836+0200
2022-04-29T13:48:31.836+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] vsphere_virtual_machine (ID = 421571f1-f9cd-870d-c116-8eda19ad3b84): Resource argument "num_cores_per_socket" requires a VM restart: timestamp=2022-04-29T13:48:31.836+0200
2022-04-29T13:48:31.836+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] vsphere_virtual_machine (ID = 421571f1-f9cd-870d-c116-8eda19ad3b84): Memory operation requires a VM restart: timestamp=2022-04-29T13:48:31.836+0200
2022-04-29T13:48:31.836+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] vsphere_virtual_machine (ID = 421571f1-f9cd-870d-c116-8eda19ad3b84): Resource argument "swap_placement_policy" requires a VM restart: timestamp=2022-04-29T13:48:31.836+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] vsphere_virtual_machine (ID = 421571f1-f9cd-870d-c116-8eda19ad3b84): Resource argument "firmware" requires a VM restart: timestamp=2022-04-29T13:48:31.836+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] NormalizeBus: Normalizing first 1 controllers on SCSI bus to device type pvscsi: timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] NormalizeBus: Normalizing first 0 controllers on SATA bus: timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] NormalizeBus: Normalizing first 2 controllers on IDE bus: timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] NormalizeBus: Current SCSI bus contents: pvscsi-1000: timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] NormalizeBus: Current SATA bus contents:: timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] NormalizeBus: Current IDE bus contents: device-200,device-201: timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] NormalizeBus: Outgoing device list: ide-200,ide-201,ps2-300,pci-100,sio-400,keyboard-600,pointing-700,video-500,vmci-12000,pvscsi-1000,cdrom-3000,disk-1000-0,ethernet-0: timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] NormalizeBus: Outgoing device config spec:: timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] DiskPostCloneOperation: Looking for disk device changes post-clone: timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] DiskRefreshOperation: Found controller "controller-1000" for device "disk-1000-0": timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] DiskPostCloneOperation: Disk devices located: disk-1000-0: timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] DiskPostCloneOperation: Disk devices order after sort: disk-1000-0: timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] DiskPostCloneOperation: Current resource set: (key 2000 at scsi:0:0): timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] DiskPostCloneOperation: Resource set order after sort: (key 2000 at scsi:0:0): timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] DiskPostCloneOperation: Looking for and applying device changes in source disks: timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] disk.0 (key 2000 at scsi:0:0) (<unknown>): Reading state: timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] FindVirtualDevice: Looking for device with key 2000: timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] FindVirtualDevice: Device found: disk-1000-0: timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] Locating virtual machine with UUID "421571f1-f9cd-870d-c116-8eda19ad3b84": timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:31.837+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:31 [DEBUG] Using SearchIndex to look up UUID "421571f1-f9cd-870d-c116-8eda19ad3b84": timestamp=2022-04-29T13:48:31.837+0200
2022-04-29T13:48:32.041+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:32 [DEBUG] VM "//SOMEDC/vm/app-server-test" found for UUID "421571f1-f9cd-870d-c116-8eda19ad3b84": timestamp=2022-04-29T13:48:32.041+0200
2022-04-29T13:48:32.441+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:32 [DEBUG] queryAssociatedProfile: Retrieving storage policy of server object of type [virtualDiskId] and key [vm-41690:2000].: timestamp=2022-04-29T13:48:32.441+0200
2022-04-29T13:48:32.563+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:32 [DEBUG] vsphere_virtual_machine (ID = 421571f1-f9cd-870d-c116-8eda19ad3b84): Performing delete: timestamp=2022-04-29T13:48:32.563+0200
2022-04-29T13:48:32.563+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:32 [DEBUG] Locating virtual machine with UUID "421571f1-f9cd-870d-c116-8eda19ad3b84": timestamp=2022-04-29T13:48:32.563+0200
2022-04-29T13:48:32.563+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:32 [DEBUG] Using SearchIndex to look up UUID "421571f1-f9cd-870d-c116-8eda19ad3b84": timestamp=2022-04-29T13:48:32.563+0200
2022-04-29T13:48:32.764+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:32 [DEBUG] VM "//SOMEDC/vm/app-server-test" found for UUID "421571f1-f9cd-870d-c116-8eda19ad3b84": timestamp=2022-04-29T13:48:32.764+0200
2022-04-29T13:48:32.764+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:32 [DEBUG] Fetching properties for VM "//SOMEDC/vm/app-server-test": timestamp=2022-04-29T13:48:32.764+0200
2022-04-29T13:48:32.962+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:32 [DEBUG] DiskDestroyOperation: Beginning destroy: timestamp=2022-04-29T13:48:32.962+0200
2022-04-29T13:48:32.962+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:32 [DEBUG] DiskDestroyOperation: Detaching devices with keep_on_remove enabled: timestamp=2022-04-29T13:48:32.962+0200
2022-04-29T13:48:32.962+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:32 [DEBUG] DiskDestroyOperation: Device config operations from destroy:: timestamp=2022-04-29T13:48:32.962+0200
2022-04-29T13:48:32.962+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:32 [DEBUG] Deleting virtual machine "//SOMEDC/vm/app-server-test": timestamp=2022-04-29T13:48:32.962+0200
2022-04-29T13:48:33.908+0200 [INFO]  provider.terraform-provider-vsphere: 2022/04/29 13:48:33 [DEBUG] vsphere_virtual_machine (ID = <new resource>): Delete complete: timestamp=2022-04-29T13:48:33.908+0200
2022-04-29T13:48:33.934+0200 [ERROR] vertex "module.app-server.vsphere_virtual_machine.app-server-test" error: error reconfiguring virtual machine: error processing disk changes post-clone: disk.0: ServerFaultCode: NoPermission: RESOURCE (vm-41690:2000), ACTION (queryAssociatedProfile): RESOURCE (vm-41690), ACTION (PolicyIDByVirtualDisk)
╷
│ Error: error reconfiguring virtual machine: error processing disk changes post-clone: disk.0: ServerFaultCode: NoPermission: RESOURCE (vm-41690:2000), ACTION (queryAssociatedProfile): RESOURCE (vm-41690), ACTION (PolicyIDByVirtualDisk)

Panic Output

No response

Expected Behavior

VM should create successfully

Actual Behavior

VM creation fails post-clone

References

974

github-actions[bot] commented 2 years ago

Hello,   slavina-rumenova ! 🖐

Thank you for submitting an issue for this provider. The issue will now enter into the issue lifecycle.

If you want to contribute to this project, please review the contributing guidelines and information on submitting pull requests.

tenthirtyam commented 2 years ago

This does seem the be related the StorageProfile privileges per the debug.

Are you running the plan under the context of administrator@vsphere.local or a user assigned the Administrator role?

If neither, can you provide a detailed list of the privileges or default role assigned to the account under which the plan is configured?

Ryan Johnson Staff II Solutions Architect | VMware, Inc.

slavina-rumenova commented 2 years ago

I'm running the plan under a user assigned the Administrator role via an AD group (permissions are handled by our vcenter admins via AD groups and my user is part of a group which should have Administrator rights on all VMs in the DC).

Here's a list of all the rights that I have:

Alarm.Acknowledge
Datastore.AllocateSpace
Datastore.Browse
Datastore.DeleteFile
Datastore.FileManagement
Datastore.UpdateVirtualMachineFiles
Datastore.UpdateVirtualMachineMetadata
Folder.Create
Folder.Delete
Folder.Move
Folder.Rename
Global.SetCustomField
InventoryService.Tagging.ObjectAttachable
Network.Assign
Resource.ApplyRecommendation
Resource.AssignVAppToPool
Resource.AssignVMToPool
StoragePod.Config
StorageProfile.Update
StorageProfile.View
StorageViews.View
System.Anonymous
System.Read
System.View
VApp.ApplicationConfig
VApp.AssignResourcePool
VApp.AssignVApp
VApp.AssignVM
VApp.Clone
VApp.Create
VApp.Delete
VApp.Export
VApp.ExtractOvfEnvironment
VApp.Import
VApp.InstanceConfig
VApp.ManagedByConfig
VApp.Move
VApp.PowerOff
VApp.PowerOn
VApp.Rename
VApp.ResourceConfig
VApp.Suspend
VApp.Unregister
VirtualMachine.Config.AddExistingDisk
VirtualMachine.Config.AddNewDisk
VirtualMachine.Config.AddRemoveDevice
VirtualMachine.Config.AdvancedConfig
VirtualMachine.Config.Annotation
VirtualMachine.Config.CPUCount
VirtualMachine.Config.ChangeTracking
VirtualMachine.Config.DiskExtend
VirtualMachine.Config.DiskLease
VirtualMachine.Config.EditDevice
VirtualMachine.Config.HostUSBDevice
VirtualMachine.Config.ManagedBy
VirtualMachine.Config.Memory
VirtualMachine.Config.MksControl
VirtualMachine.Config.QueryFTCompatibility
VirtualMachine.Config.QueryUnownedFiles
VirtualMachine.Config.RawDevice
VirtualMachine.Config.ReloadFromPath
VirtualMachine.Config.RemoveDisk
VirtualMachine.Config.Rename
VirtualMachine.Config.ResetGuestInfo
VirtualMachine.Config.Resource
VirtualMachine.Config.Settings
VirtualMachine.Config.SwapPlacement
VirtualMachine.Config.ToggleForkParent
VirtualMachine.Config.Unlock
VirtualMachine.Config.UpgradeVirtualHardware
VirtualMachine.GuestOperations.Execute
VirtualMachine.GuestOperations.Modify
VirtualMachine.GuestOperations.ModifyAliases
VirtualMachine.GuestOperations.Query
VirtualMachine.GuestOperations.QueryAliases
VirtualMachine.Hbr.ConfigureReplication
VirtualMachine.Hbr.MonitorReplication
VirtualMachine.Hbr.ReplicaManagement
VirtualMachine.Interact.AnswerQuestion
VirtualMachine.Interact.Backup
VirtualMachine.Interact.ConsoleInteract
VirtualMachine.Interact.CreateScreenshot
VirtualMachine.Interact.CreateSecondary
VirtualMachine.Interact.DefragmentAllDisks
VirtualMachine.Interact.DeviceConnection
VirtualMachine.Interact.DisableSecondary
VirtualMachine.Interact.DnD
VirtualMachine.Interact.EnableSecondary
VirtualMachine.Interact.GuestControl
VirtualMachine.Interact.MakePrimary
VirtualMachine.Interact.Pause
VirtualMachine.Interact.PowerOff
VirtualMachine.Interact.PowerOn
VirtualMachine.Interact.PutUsbScanCodes
VirtualMachine.Interact.Record
VirtualMachine.Interact.Replay
VirtualMachine.Interact.Reset
VirtualMachine.Interact.SESparseMaintenance
VirtualMachine.Interact.SetCDMedia
VirtualMachine.Interact.SetFloppyMedia
VirtualMachine.Interact.Suspend
VirtualMachine.Interact.SuspendToMemory
VirtualMachine.Interact.TerminateFaultTolerantVM
VirtualMachine.Interact.ToolsInstall
VirtualMachine.Interact.TurnOffFaultTolerance
VirtualMachine.Inventory.Create
VirtualMachine.Inventory.CreateFromExisting
VirtualMachine.Inventory.Delete
VirtualMachine.Inventory.Move
VirtualMachine.Inventory.Register
VirtualMachine.Inventory.Unregister
VirtualMachine.Namespace.Event
VirtualMachine.Namespace.EventNotify
VirtualMachine.Namespace.Management
VirtualMachine.Namespace.ModifyContent
VirtualMachine.Namespace.Query
VirtualMachine.Namespace.ReadContent
VirtualMachine.Provisioning.Clone
VirtualMachine.Provisioning.CloneTemplate
VirtualMachine.Provisioning.CreateTemplateFromVM
VirtualMachine.Provisioning.Customize
VirtualMachine.Provisioning.DeployTemplate
VirtualMachine.Provisioning.DiskRandomAccess
VirtualMachine.Provisioning.DiskRandomRead
VirtualMachine.Provisioning.FileRandomAccess
VirtualMachine.Provisioning.GetVmFiles
VirtualMachine.Provisioning.MarkAsTemplate
VirtualMachine.Provisioning.MarkAsVM
VirtualMachine.Provisioning.ModifyCustSpecs
VirtualMachine.Provisioning.PromoteDisks
VirtualMachine.Provisioning.PutVmFiles
VirtualMachine.Provisioning.ReadCustSpecs
VirtualMachine.Replication.com.vmware.vcDr.Protect
VirtualMachine.Replication.com.vmware.vcDr.Unprotect
VirtualMachine.State.CreateSnapshot
VirtualMachine.State.RemoveSnapshot
VirtualMachine.State.RenameSnapshot
VirtualMachine.State.RevertToSnapshot

StorageProfile.[View|Update] are granted, this should be enough, right?

tenthirtyam commented 2 years ago

You may wish to check against https://github.com/hashicorp/terraform-provider-vsphere/issues/1666 which has a list of privileges used for r/virtual_machine resource on one user's environment.

Ryan Johnson Staff II Solutions Architect | VMware, Inc.

slavina-rumenova commented 2 years ago

I do have both privileges mentioned in the issue that were the issue: 

VirtualMachine.Config.SwapPlacement
StorageProfile.View

The only ones that I am missing compared to the other user are:

Host.Local.CreateVM
Host.Local.DeleteVM
Host.Local.ReconfigVM

However, as they are not related to StorageProfile, I doubt this is the issue

tenthirtyam commented 2 years ago

Hi @slavina-rumenova - are you still experiencing this issue?

Ryan Johnson Senior Staff Solutions Architect | Product Engineering @ VMware, Inc.

slavina-rumenova commented 2 years ago

No, it turned out to be permissions after all. Even though I had StorageProfile.[View|Update] on a second level sphere element, that's not enough. One needs the StorageProfile permissions on the top level vsphere element in the hierarchy. After I was granted this, all worked fine.

github-actions[bot] commented 2 years ago

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.