Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 903039

Summary: JON Agent RPM Errata Failure(s): SRPM
Product: [JBoss] JBoss Operations Network Reporter: Mike Foley <mfoley>
Component: AgentAssignee: Simeon Pinder <spinder>
Status: CLOSED EOL QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: medium    
Version: JON 3.1.2CC: myarboro
Target Milestone: ---   
Target Release: JON 4.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-24 15:06:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
SRPM failure none

Description Mike Foley 2013-01-23 01:07:42 UTC
Created attachment 685548 [details]
SRPM failure

Description of problem:   Errata TPS test failure with SRPM tests 


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



Steps to Reproduce:
1.  TPS tests 

  
Actual results:  test failure.  see attached 


Expected results:  All TPS tests pass ... 


Additional info:



Looking further at the SRPM failures here
http://nest.test.redhat.com/mnt/qa/scratch/TPS-x86-64-rhevm31/2012:14315/tps/tps-srpmtest.html#Source Ship Inclusion-1-1-0

I do remember waiving this failure for the last errata we did. 
Basically the ET tool is configured for the JON product to not let
it publish the SRC to ftp.redhat.com. I don't remember why nor who did it. 
It will be nice to get this fixed as its a simple config change on the ET side
to let this SRPM goto ftp. But its not a roadblock. Can be waived.

Comment 3 Filip Brychta 2019-06-24 15:06:04 UTC
JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.