Project

General

Profile

Actions
Copy link

Refactor #19994

closed

Move openscap component initialization into a separate service

Added by Ondřej Pražák over 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ondřej Pražák
Target version:
smart_proxy_openscap 0.6.5
Branch:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
https://github.com/theforeman/smart_proxy_openscap/pull/50
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

On proxy, we call OpenSCAP.oscap_init, which makes a call to xmlInitParser(), but libxml2 docs state that it is not reentrant. We should make changes so that oscap_init is called once during module initialization and oscap_cleanup is called during shutdown to avoid potential problems that could arie due to the fact that proxy is multithreaded.

Related issues 1 (0 open — 1 closed)

Related to OpenSCAP - Bug #19708: StorageFS does not destroy objects from ruby-openscapRejectedOndřej Pražák05/30/2017Actions
Actions
Copy link
 #1

Updated by The Foreman Bot over 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/smart_proxy_openscap/pull/50 added
Actions
Copy link
 #2

Updated by Ondřej Pražák over 7 years ago

  • Related to Bug #19708: StorageFS does not destroy objects from ruby-openscap added
Actions
Copy link
 #3

Updated by Marek Hulán over 7 years ago

  • Target version changed from 1.13.4 to 1.14.0
Actions
Copy link
 #4

Updated by Marek Hulán over 7 years ago

  • Target version changed from 1.14.0 to 1.14.3
Actions
Copy link
 #5

Updated by Marek Hulán over 7 years ago

  • Translation missing: en.field_release set to 254
Actions
Copy link
 #6

Updated by Marek Hulán over 7 years ago

  • Target version changed from 1.14.3 to 1.17.0-RC2
Actions
Copy link
 #7

Updated by Ondřej Pražák over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF