Description of problem: vnic_profile_mappings should use verbal network/profile name instead of the internal profile id Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Register vnic profile with mapping 2. 3. Actual results: Use target profile id Expected results: Use verbal target profile id Additional info:
We still have quite a bit of ironing down to do, so this is unlikely to arrive at 4.2.1.
Created attachment 1394060 [details] flow chart of selecting target vnic profile with 'allow partial import' the flow chart describes the functionality executed by the engine on import vm\template
Created attachment 1394061 [details] flow chart of selecting target vnic profile without 'allow partial import' this flow chart describes the functionality executed by the engine on import\vmtemplate when the user does not specify 'allow partial import'
Created attachment 1407111 [details] flow chart of selecting target vnic profile for single vnic flow chart of selecting target vnic profile for single vnic
Verified on - 4.2.2.4-0.1.el7
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.