Reconfiguring a virtual machine managed by vRealize Automation fails with an exception
stating
"The data specified within the request is invalid.The number of nics you requested are more than specified in the blueprint that was used to provision this machine"
In vRealize Automation 7.5 , when any Day-2 actions are performed ( Change of CPU / Memory , Network etc.. ) , the network size is always checked against the blueprint maximum allowed for the VM.
Above exception is thrown when a given VM has more than the maximum nics allowed.
vRA will not allow the max nics to be exceeded at any point in time. Even when vRA is not performing any Day-2 action on the nics , it still performs the network size check and throws an exception.
This behaviour has been changed in vRealize Automation 7.6
In this version a network check is ONLY performed when a network change is being performed through Day-2 actions. If other attributes are being changed other than networks then the network size check wouldn't be performed.
Comentarios