Bug 2222725

Summary: Confusing Error Message when content-export fails due to unsynced repository
Product: Red Hat Satellite Reporter: Sam Bible <sbible>
Component: Inter Satellite SyncAssignee: Jeremy Lenz <jlenz>
Status: CLOSED ERRATA QA Contact: Sam Bible <sbible>
Severity: medium Docs Contact:
Priority: medium    
Version: NightlyCC: ahumbe, chiggins, iballou, jlenz, rlavi, shwsingh
Target Milestone: 6.15.0Flags: rlavi: needinfo? (chiggins)
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: Environment:
Last Closed: 2024-04-23 17:11:39 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:

Description Sam Bible 2023-07-13 14:52:07 UTC 
Description of problem:
When attempting to run `hammer content-export` on a Content View containing a Repository that is either unsynced, or that has it's Download Policy set to On-Demand, an unhelpful error message is returned:
undefined method `first' for nil:NilClass
This could cause confusion for customers, as it looks like a serious error, but it is expected.

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

How reproducible:
100%

Steps to Reproduce:
1. Sync some repository like Satellite Client, and ensure that the download policy is set to On Demand
2. Create a Content View, attach the Repo, and publish a version
3. SSH into the Satellite, and run the command: `hammer content-export complete version --content-view="<CV Name>" --version=<CV Version> --organization="<Org Name"

Actual results:
Error: Remote artifacts cannot be exported.
undefined method `first' for nil:NilClass
Is returned as the error message.

Expected results:
Perhaps only the first line, and not the undefined method line; could also give some better explanation for the cause.
Comment 1 Jeremy Lenz 2023-07-14 17:13:11 UTC 
Connecting redmine issue https://projects.theforeman.org/issues/36162 from this bug
Comment 2 Bryan Kearney 2023-09-21 20:02:43 UTC 
Upstream bug assigned to jlenz
Comment 3 Bryan Kearney 2023-09-21 20:02:46 UTC 
Upstream bug assigned to jlenz
Comment 4 Bryan Kearney 2023-10-03 20:02:43 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36162 has been resolved.
Comment 5 Brad Buckingham 2023-10-09 12:22:59 UTC 
Hi Shweta,

Per our conversation in triage, you mentioned that this may be fixed in 6.14.0.  I am adding this needinfo as a reminder to perform a quick check/verification.  If it is resolved in 6.14.0, we can triage to that release and mark verified; otherwise, we can revisit in our next triage session.

Thanks!
Comment 12 errata-xmlrpc 2024-04-23 17:11:39 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.15.0 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2024:2010