r/virtual_machine: Device cull range fix, and handle zero-NIC templates #269
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was some issues with our device culling/ranging logic in certain
scenarios:
result. This was the result of these values being pointers because we
work with the unit number value directly in the virtual device, which is
a pointer. This fixes things so that if a zero-length device list is
passed to unit range, we return 0 immediately (as there are no devices
to range over).
needed by configuration, the device cull range expression (which is used
to handle the exact opposite scenario) was running into out-of-range
issues. This has been fixed by asserting that the old device list is
indeed longer than the new device list so that there's no way that
referencing old[len(new):] will fail. This has been extended to CD
devices too, which has the same logic, even though it's currently masked
by the fact that we only allow one cdrom device.
Fixes #267.