Bug 1377728

Summary: Error refreshing manifest. Runtime Error null at org.candlepin.sync.Exporter.exportProducts:517
Product: Red Hat Satellite Reporter: Sasha Segal <ssegal>
Component: CandlepinAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WORKSFORME QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: high    
Version: 6.2.0CC: abraverm, bbuckingham, csnyder, jcallaha, ssegal
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1380507 1380508 (view as bug list) Environment:
Last Closed: 2016-09-30 14:23:25 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:
Bug Depends On: 1380507    
Bug Blocks: 1338516    
Attachments:
Description Flags
Screenshot of error
none
Foreman debug log none

Description Sasha Segal 2016-09-20 13:12:37 UTC 
Created attachment 1202887 [details]
Screenshot of error

Description of problem:
Unable to refresh Subscription Manifest.

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


How reproducible:

Always.

Steps to Reproduce:
1. Go to https://satellite6-ops.rhev-ci-vms.eng.rdu2.redhat.com/subscriptions/manifest/import
2. Click on "Refresh Manifest"
3.

Actual results:

Not refreshed, get error: Error refreshing manifest. Runtime Error null at org.candlepin.sync.Exporter.exportProducts:517

Expected results:

Refresh Manifest, More information if error occurs.

Additional info:
Comment 1 Sasha Segal 2016-09-20 13:16:18 UTC 
During that time Customer Portal show Maintenance screen.
Comment 2 Sasha Segal 2016-09-20 13:33:33 UTC 
Created attachment 1202890 [details]
Foreman debug log
Comment 3 Sasha Segal 2016-09-20 14:37:05 UTC 
Also we found that Manifest version was 6.1 while Satellite already upgraded to 6.2
Comment 6 Barnaby Court 2016-09-22 19:20:36 UTC 
This appears to have been a transient issue. Please refresh the org in the portal and then retry the manifest export.
Comment 7 Sasha Segal 2016-09-24 09:13:35 UTC 
The issue solved after Portal support fixed issue with Portal, I was able export correct manifest (6.2 for installed 6.2). With correct manifest all works.
Comment 8 Chris Snyder 2016-09-30 14:23:25 UTC 
This was fixed with the fix to the upstream data.