Bug 1269413 - running master on FC22 server.log shows several warnings about java modules.
Summary: running master on FC22 server.log shows several warnings about java modules.
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.0.0-alpha
: 4.0.0
Assignee: Juan Hernández
QA Contact: Pavel Stehlik
Depends On:
TreeView+ depends on / blocked
Reported: 2015-10-07 09:39 UTC by Sandro Bonazzola
Modified: 2016-07-26 11:05 UTC (History)
5 users (show)

Fixed In Version: ovirt 4.0.0 alpha1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-07-26 11:05:08 UTC
oVirt Team: Infra
oourfali: ovirt-4.0.0?
ylavi: planning_ack+
oourfali: devel_ack+
sbonazzo: testing_ack?

Attachments (Terms of Use)
warnings in server.log (36.09 KB, text/plain)
2015-10-07 09:39 UTC, Sandro Bonazzola
no flags Details

System ID Private Priority Status Summary Last Updated
oVirt gerrit 47111 0 master MERGED core: Disable warnings about private modules Never

Description Sandro Bonazzola 2015-10-07 09:39:55 UTC
Created attachment 1080562 [details]
warnings in server.log

Description of problem:
running master on FC22 server.log shows several warnings about java modules.
The warning are probably harmless but I think they're worth to be reviewed and addressed if possible.

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

How reproducible:

Steps to Reproduce:
1. engine-setup
2. check server.log

Actual results:
See attachment.

Expected results:
No warning or at least a reduced number of warnings

Additional info:

Comment 1 Oved Ourfali 2015-10-08 05:23:06 UTC
Juan - can you have a look?

Comment 2 Juan Hernández 2015-10-08 08:14:42 UTC
I think that this isn't a serious issue, and that it isn't worth fixing. But if we want to avoid those messages we have several alternatives:

1. Stop using the modules provided by JBoss. This doesn't make any sense, in my opinion.

2. Create copies of the modules provided by JBoss, and use those instead of the original ones. This doesn't make sense either.

3. Mute the logging category that issues that warning. That is what the proposed patch does.

Comment 3 Oved Ourfali 2015-10-08 08:25:37 UTC
I totally agree.

Comment 4 Lukas Svaty 2016-07-26 11:05:08 UTC
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA

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