Ohai,

the tests for smart_proxy currently fail when executed with OpenSCAP
>= 1.2.11 (like in EL6 or Fedora 25):

Error: test_scap_content_guide(ScapContentParserApiTest):
  JSON::ParserError: 784: unexpected token at 'Error occurred:
Internal error: Could not acquire handle to xccdf.xml source.
[ds_sds_session.c:357]
  '
/home/remote/egolov/.gem/ruby/gems/json-1.8.6/lib/json/common.rb:155:in `parse'
/home/remote/egolov/.gem/ruby/gems/json-1.8.6/lib/json/common.rb:155:in `parse'
/tmp/smart_proxy_openscap/test/scap_content_parser_api_test.rb:50:in
`test_scap_content_guide'
     47:
     48:   def test_scap_content_guide
     49:     post
'/scap_content/guide/xccdf_org.ssgproject.content_profile_rht-ccp',
@scap_content, 'CONTENT_TYPE' => 'text/xml'
  => 50:     result = JSON.parse(last_response.body)
     51:     assert(result['html'].start_with?('<!DOCTYPE html>'))
     52:     assert(last_response.successful?)
     53:   end

Seems that Marek did hit that issue at some point too:
http://projects.theforeman.org/issues/17839

It works fine with OpenSCAP 1.2.9 (Debian Stretch) and 1.2.10 (EL7),
but will terribly fail on EL6 (1.2.13) and Fedora 25 (1.2.14).
Pulling builds from Koji I tracked that down to 1.2.11 being the
culprit, a proper bisect between 1.2.10 and 1.2.11 is yet outstanding.
And I guess an OpenSCAP update in EL7 is coming at some point too.

I am yet unsure if that is us doing something fishy, or whether it is
an actual bug in OpenSCAP.

Cheers
Evgeni

-- 
Beste Grüße/Kind regards,

Evgeni Golov
Software Engineer
________________________________________________________________________
Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael
O'Neill, Eric Shander

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to