Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1347931

Summary: REST-API V4 | Missing network_filter <name> when creating vnic profile with default filter
Product: [oVirt] ovirt-engine Reporter: Meni Yakove <myakove>
Component: RestAPIAssignee: Juan Hernández <juan.hernandez>
Status: CLOSED CURRENTRELEASE QA Contact: Meni Yakove <myakove>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0.0CC: alkaplan, bugs, juan.hernandez
Target Milestone: ovirt-4.0.1Keywords: Automation
Target Release: 4.0.1.1Flags: rule-engine: ovirt-4.0.z+
rule-engine: planning_ack+
juan.hernandez: devel_ack+
rule-engine: testing_ack+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 06:23:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Meni Yakove 2016-06-18 16:44:37 UTC
Description of problem:
When creating vnic profile with default filter (UI or rest) the return from REST GET is missing the network_filter name.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<vnic_profiles>
    <vnic_profile href="/ovirt-engine/api/vnicprofiles/7087091c-a64c-4a31-b3fe-8dea87ed0596" id="7087091c-a64c-4a31-b3fe-8dea87ed0596">
        <name>default_filter</name>
        <link href="/ovirt-engine/api/vnicprofiles/7087091c-a64c-4a31-b3fe-8dea87ed0596/permissions" rel="permissions"/>
        <pass_through>
            <mode>disabled</mode>
        </pass_through>
        <port_mirroring>false</port_mirroring>
        <network href="/ovirt-engine/api/networks/2a65ed33-c285-4084-bf81-e2f1f80b0c10" id="2a65ed33-c285-4084-bf81-e2f1f80b0c10"/>
        <network_filter href="/ovirt-engine/api/networkfilters/0000001a-001a-001a-001a-00000000036b" id="0000001a-001a-001a-001a-00000000036b"/>
    </vnic_profile>



    <vnic_profile href="/ovirt-engine/api/vnicprofiles/5db48caa-cec5-475d-a41f-1e74cf21042f" id="5db48caa-cec5-475d-a41f-1e74cf21042f">
        <name>non_default_filter</name>
        <link href="/ovirt-engine/api/vnicprofiles/5db48caa-cec5-475d-a41f-1e74cf21042f/permissions" rel="permissions"/>
        <pass_through>
            <mode>disabled</mode>
        </pass_through>
        <port_mirroring>false</port_mirroring>
        <network href="/ovirt-engine/api/networks/2a65ed33-c285-4084-bf81-e2f1f80b0c10" id="2a65ed33-c285-4084-bf81-e2f1f80b0c10"/>
        <network_filter href="/ovirt-engine/api/networkfilters/0000001b-001b-001b-001b-0000000000eb" id="0000001b-001b-001b-001b-0000000000eb">
            <name>allow-arp</name>
        </network_filter>
    </vnic_profile>
</vnic_profiles>



Version-Release number of selected component (if applicable):
rhevm-4.0.0.4-0.1.el7ev.noarch

Steps to Reproduce:
1. Create vnic profile with default network filter
2. API GET ovirt-engine/api/vnicprofiles/

Comment 1 Juan Hernández 2016-06-18 18:59:23 UTC
Actually I believe that the bug is including the name in some of the links. In general the links used in the API only include the "id" and "href". Additional attributes or elements are only allowed when required for backwards compatibility, and this isn't the case.

In order to get the name of the network filter (or any other attribute) the user must follow the link to the top level "networkfilters" collection.

Comment 2 Meni Yakove 2016-07-02 09:58:36 UTC
rhevm-4.0.2-0.2.rc1.el7ev.noarch

Comment 3 Sandro Bonazzola 2016-07-19 06:23:22 UTC
Since the problem described in this bug report should be
resolved in oVirt 4.0.1 released on July 19th 2016, it has been closed with a
resolution of CURRENT RELEASE.

For information on the release, and how to update to this release, follow the link below.

If the solution does not work for you, open a new bug report.

http://www.ovirt.org/release/4.0.1/