-
Notifications
You must be signed in to change notification settings - Fork 11
Closed
1 / 11 of 1 issue completedLabels
area/computeCompute and virtualization specific issues and enhancements.Compute and virtualization specific issues and enhancements.area/iaasIssues related to IronCore IaaS development.Issues related to IronCore IaaS development.area/storageStorage solutions and related concerns.Storage solutions and related concerns.questionFurther information is requestedFurther information is requested
Milestone
Description
Question?
Verify if the Volume size information reaches the libvirt-provider.
The Volume size information should be transported correctly in the storage Volume API by the Volume-brokers but I think we still have some issues in the compute Volume flow.
If I'm not mistaken the information
ironcoreVolume.Status.Access = &storagev1alpha1.VolumeAccess{
SecretRef: secretRef,
Driver: remote.Driver,
Handle: remote.Handle,
VolumeAttributes: remote.Attributes,
}
is only being updated if a Volume is being attached/detached to a machine. This is not sufficient if we need an update if the Volume resize happens on an already attached Volume.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/computeCompute and virtualization specific issues and enhancements.Compute and virtualization specific issues and enhancements.area/iaasIssues related to IronCore IaaS development.Issues related to IronCore IaaS development.area/storageStorage solutions and related concerns.Storage solutions and related concerns.questionFurther information is requestedFurther information is requested