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

Bug 1281736

Summary: CLI is flooding server log by errors
Product: [oVirt] ovirt-engine Reporter: Ondra Machacek <omachace>
Component: RestAPIAssignee: Juan Hernández <juan.hernandez>
Status: CLOSED WONTFIX QA Contact: Pavel Stehlik <pstehlik>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.6.0.2CC: bugs, oourfali
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: sbonazzo: ovirt-4.1-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-04 05:57:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ondra Machacek 2015-11-13 10:48:49 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
rhevm-cli-3.6.0.0-1.el6ev.noarch

How reproducible:
always

Steps to Reproduce:
1. In cli run: show datacenter dc
2. See /var/log/ovirt-engine/server.log

Actual results:
Trace that /ovirt-engine/api/datacenters/dc doesn't exists.

Expected results:
No trace.

Additional info:
Comment 1 Juan Hernández 2015-11-13 12:09:08 UTC 
This is an engine issue, not CLI. Whatever is the order of the requests sent by the CLI the engine should react correctly.

I think that this shouldn't block verification bug 1241117, as the only effect is extract information in the log of the engine.
Comment 2 Juan Hernández 2015-11-13 13:11:03 UTC 
Currently when we receive an identifier from the caller we try to convert it to an UUID, calling the "asGuidOr404" method. If the conversion fails then we throw a "WebApplicationException" that is captured by the server (by Resteasy) and converted into a 404 HTTP error response. We do this in many places. In addition Resteasy also sends a message to the log. This behavior can be changed throwing a "NoLogWebApplicationException" instead, but this is Resteasy specific and we don't want to re-introduce dependencies on Resteasy specific things. As the effect isn't a serious problem, just additional information in server.log, I think we should postpone this to at least 4.0.
Comment 3 Oved Ourfali 2016-09-04 05:57:01 UTC 
I don't think this should be prioritized, and as we're deprecating the CLI I suggest to close as wontfix.