[X] I have read and agree to the project's Code of Conduct.
[X] Vote on this issue by adding a š reaction to the original issue initial description to help the maintainers prioritize.
[X] Do not leave "+1" or other comments that do not add relevant information or questions.
[X] If you are interested in working on this issue or have submitted a pull request, please leave a comment.
VMware Cloud Foundation
v4.5.2
Environment Details
No response
Description
The cmdlet Request-VmConnectedCdrom in the reporting module only reports the VMs on which the CD ROM is connected.
The same information is sent to vrops.
e.g. Lets say we have 2 VMs with drives connected, the information is updated on corresponding objects of those 2 VMs on vrops.
Now if the user disconnects the drive from one of the VMs, and when HRM runs again in the next cycle, the Request-VmConnectedCdrom will report only 1 VM with drive connected. It will not report the other VM. So, on vrops, stale information will continue to exist and will not be removed as we didnt know which VM didnt have the drive connected.
The Request-VmConnectedCdrom needs to be changed to report all vms with drive state as either N/A if no drive is connected, or report the ISO path if drive is connected.
Updated corresponding code in for Reporting Module. Table will display all the VMs, so that the VM status can be updated if a connected CD ROM is removed.
Code of Conduct
VMware Cloud Foundation
v4.5.2
Environment Details
No response
Description
The cmdlet Request-VmConnectedCdrom in the reporting module only reports the VMs on which the CD ROM is connected. The same information is sent to vrops.
e.g. Lets say we have 2 VMs with drives connected, the information is updated on corresponding objects of those 2 VMs on vrops.
Now if the user disconnects the drive from one of the VMs, and when HRM runs again in the next cycle, the Request-VmConnectedCdrom will report only 1 VM with drive connected. It will not report the other VM. So, on vrops, stale information will continue to exist and will not be removed as we didnt know which VM didnt have the drive connected.
The Request-VmConnectedCdrom needs to be changed to report all vms with drive state as either N/A if no drive is connected, or report the ISO path if drive is connected.
Expected Behavior
NA
Actual Behavior
NA
Steps to Reproduce
No response
Screenshots
No response
References
No response