Project

General

Profile

Actions

Incident #2287

closed

registry-publisher-1.2.6-3.10.1.jar still contains the broken log4j.properties

Added by Andrea Dell'Amico about 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Urgent
Category:
Application
Start date:
Feb 18, 2016
Due date:
% Done:

100%

Estimated time:
Infrastructure:
Development, Pre-Production, Production

Description

registry-publisher-1.2.6-3.10.1.jar as found in the smartgears 1.2.7-3.10.1 distribution still carry the log4j.properties file that breaks the log4j global configuration.

I've pushed a fixed version on the ansible git repository and I'm using that file to overwrite the original one so that we can proceed provisioning the dataminer nodes, while waiting for a proper fix.

Actions #2

Updated by Roberto Cirillo about 9 years ago

  • Status changed from New to In Progress
Actions #3

Updated by Roberto Cirillo about 9 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

The new smartgears-distribution version: 1.2.7-3.10.1, is now available on nexus. (repository gcube-staging).
This new version contains the registry-publisher 1.2.6-3.10.1 without the log4j properties file.
It also doesn't contain the library "common-smartgears-utils".

Actions #4

Updated by Andrea Dell'Amico about 9 years ago

Thanks. I removed the workaround from the playbook.
I cannot test it on the production dataminer, but I think we can test on a dev host when possible.

Actions #5

Updated by Roberto Cirillo about 9 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)