Before executing the relevant FollowLink method, make sure the response we got from the engine is not nil, otherwise the response object will be nil and panic.
Alternate Designs
Benefits
This is a bug fix. If ovirt-engine is not accessible before a FollowLink call, it will panic because the response object will be nil.
Possible Drawbacks
Verification Process
This can be reproduced easily by terminating the ovirt-engine process right before the FollowLink call, an example stack trace would look like this:
Description of the Change
Before executing the relevant FollowLink method, make sure the response we got from the engine is not nil, otherwise the response object will be nil and panic.
Alternate Designs
Benefits
This is a bug fix. If ovirt-engine is not accessible before a FollowLink call, it will panic because the response object will be nil.
Possible Drawbacks
Verification Process
This can be reproduced easily by terminating the ovirt-engine process right before the FollowLink call, an example stack trace would look like this:
I used this snippet[1] to reproduce, with my patch the result is:
https://gist.github.com/bennyz/d5b5f5112aa4b1ea27b6dc41791a8fab
Applicable Issues