Bug 1281736 - CLI is flooding server log by errors
CLI is flooding server log by errors
Product: ovirt-engine
Classification: oVirt
Component: RestAPI (Show other bugs)
Unspecified Unspecified
unspecified Severity low (vote)
: ovirt-4.1.0-alpha
: ---
Assigned To: Juan Hernández
Pavel Stehlik
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2015-11-13 05:48 EST by Ondra Machacek
Modified: 2016-09-04 01:57 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-09-04 01:57:01 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
oourfali: ovirt‑4.1?
omachace: planning_ack?
omachace: devel_ack?
omachace: testing_ack?

Attachments (Terms of Use)

  None (edit)
Description Ondra Machacek 2015-11-13 05:48:49 EST
Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:

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 07:09:08 EST
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 08:11:03 EST
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 01:57:01 EDT
I don't think this should be prioritized, and as we're deprecating the CLI I suggest to close as wontfix.

Note You need to log in before you can comment on or make changes to this bug.