winterhazel opened a new pull request, #7831: URL: https://github.com/apache/cloudstack/pull/7831
### Description After a backup is successfully restored in Veeam, CloudStack tries to synchronize the restored VM; however, during the NIC synchronization process, all NIC devices are cast to `VirtualE1000`, whether they are an `E1000` or not, resulting in a casting exception being thrown and the process failing when they are not. This PR addresses the fix for this issue. ### Types of changes - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] New feature (non-breaking change which adds functionality) - [X] Bug fix (non-breaking change which fixes an issue) - [ ] Enhancement (improves an existing feature and functionality) - [ ] Cleanup (Code refactoring and cleanup, that may add test cases) ### Feature/Enhancement Scale or Bug Severity #### Feature/Enhancement Scale - [ ] Major - [ ] Minor #### Bug Severity - [ ] BLOCKER - [ ] Critical - [X] Major - [ ] Minor - [ ] Trivial ### Screenshots (if appropriate): ### How Has This Been Tested? This was tested in a local lab. Before the changes, whenever I tried to restore a backup of a VM that had a network adapter of types `PCNet32`, `Vmxnet2` or `Vmxnet3`, I would receive the following error message: ``` (<vm_name>) Error during vm backup restoration and import: class com.vmware.vim25.VirtualPCNet32 cannot be cast to class com.vmware.vim25.VirtualE1000 (com.vmware.vim25.VirtualPCNet32 and com.vmware.vim25.VirtualE1000 are in unnamed module of loader 'app') ``` With these changes, I was able to successfully restore the backups. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
