Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ovirt: Reconcile disk on USER_UPDATE_VM_DISK #646

Merged
merged 2 commits into from
Nov 12, 2023

Conversation

nijinashok
Copy link
Contributor

When a disk is extended in RHV, the size is not updated in the inventory causing the VM to be imported with old disk size. This is now solved by reconciling the disk on USER_UPDATE_VM_DISK.

https://issues.redhat.com/browse/MTV-829

When a disk is extended in RHV, the size was not updated in the inventory
causing the VM to be imported with old disk size. This is now solved
by reconciling the disk on USER_UPDATE_VM_DISK.

Signed-off-by: Nijin Ashok <[email protected]>
@nijinashok nijinashok requested a review from ahadas as a code owner November 10, 2023 06:23
Copy link
Member

@ahadas ahadas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @nijinashok !
yeah, USER_UPDATE_VM_DISK is not handled properly - we should really handle it as a disk-property change rather than a vm-change, I think we can drop it from VMAdapter's handling

The VM-specific properties (e.g., disk interface) are handled by
VMAdapter. The handling by DiskAdapter of USER_UPDATE_VM_DISK events is
for updating the disk properties that are not VM-specific, this moving
this event to the section of disk-events (minor change).

Signed-off-by: Arik Hadas <[email protected]>
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@ahadas
Copy link
Member

ahadas commented Nov 12, 2023

yeah, USER_UPDATE_VM_DISK is not handled properly - we should really handle it as a disk-property change rather than a vm-change, I think we can drop it from VMAdapter's handling

after a second look, the VM-specific properties are retrieved by VMAdapter so it should still track USER_UPDATE_VM_DISK events (there's no need to change VMAdapter). I pushed a minor change with another commit that places USER_UPDATE_VM_DISK under // Disk in the DiskAdapter

@ahadas ahadas merged commit 0874975 into kubev2v:main Nov 12, 2023
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants