Description of problem:
Support NetworkInterfaces list in the machine spec and sync those when creating the instance.
With this nodes can use different vNic profile ids and potentially different networks.
Roy, if I understand correctly, this is pretty much verified by verifying https://bugzilla.redhat.com/show_bug.cgi?id=1816714, right?
(In reply to Jan Zmeskal from comment #3)
> Roy, if I understand correctly, this is pretty much verified by verifying
> https://bugzilla.redhat.com/show_bug.cgi?id=1816714, right?
This could work, you must verify the vnic profile id you choose is really diferent than what the template has, to
make sure a real customization happended.
0. In oVirt manager, create a new vNIC profile on your network whose name is different than the network's name. Take a note of its ID.
1. Have a running OCP on RHV cluster
2. Edit spec of machineset for workers in this way:
--------> - vnic_profile_id: ad13ab27-3aae-4c65-a7e8-70b732121570
3. Delete one worker machine and make sure new one is created
4. Go to oVirt engine and check that the newly created VM has the non-default vNIC profile.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
I created a documentation bug, to publish this configuration in the documentation, bug: https://bugzilla.redhat.com/show_bug.cgi?id=1874102