Bug 1550987

Summary: link for cluster's networkfilters returns 404
Product: [oVirt] ovirt-engine Reporter: Lucie Leistnerova <lleistne>
Component: RestAPIAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.2CC: bugs, mburman
Target Milestone: ovirt-4.3.0Keywords: Automation
Target Release: 4.3.0Flags: rule-engine: ovirt-4.3+
mburman: testing_plan_complete+
mburman: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.0_alpha Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1641622 (view as bug list) Environment:
Last Closed: 2019-02-13 07:48:07 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:
Bug Depends On:    
Bug Blocks: 1641622    

Description Lucie Leistnerova 2018-03-02 13:48:03 UTC
Description of problem:
Network filters for given cluster via API can't be listed. API call returns 404 Not Found.

Version-Release number of selected component (if applicable):
ovirt-engine-restapi-4.2.2.1-0.1.el7.noarch

How reproducible: always


Steps to Reproduce:
1. list cluster via api
# curl -k -u admin@internal:xxx -H "Prefer: persistent-auth" https://engine/ovirt-engine/api/clusters

2. get networkfilters url from <links>, call it
# curl -k -u admin@internal:xxx -H "Prefer: persistent-auth" https://engine/ovirt-engine/api/clusters/b920aa73-8f04-4e13-93aa-79dea09df826/networkfilters


Actual results: 404 Not Found


Expected results: 200 and list of filters returned


Additional info:
no error in engine.log or server.log

Comment 2 Michael Burman 2018-08-21 08:15:45 UTC
Verified on - 4.3.0-0.0.master.20180819104048.git932969e.el7

Comment 3 Sandro Bonazzola 2018-11-02 14:31:44 UTC
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.7 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.

Comment 4 Sandro Bonazzola 2018-11-02 14:57:14 UTC
Closed by mistake, moving back to qa -> verified

Comment 5 Sandro Bonazzola 2019-02-13 07:48:07 UTC
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 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.