e2e, persistent-ip: Unify primary,secondary tests (primary UDNs use managedTap) #75
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.
What this PR does / why we need it:
Currently in the e2e persistent-ips the method of retrieving the IPs from the VM differs between primary and secondary UDN VMs. The reason for the difference is that primary UDN VMs did not support publishing the IPs via VMI.status.
Due to improvements in kubevirt/kubevirt the interface on vmi.status (kubevirt/kubevirt#13018) the vmi interface is now published on the vmi.status - also for primary UDN VMs.
Changing the primary UDN e2e function that retrieves the IPs to use the vmi.status allows us to simplify the e2e by unifying the function that retrieves the VMI IPs.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
This PR relies on #73
Release note: