Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2169866 - Exporting the Library environment incrementally fails with error "Incremental export can only be requested when there is a previous export or start_versions= has been specified."
Summary: Exporting the Library environment incrementally fails with error "Incremental...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Inter Satellite Sync
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 6.13.0
Assignee: Partha Aji
QA Contact: Samir Jha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-14 21:11 UTC by Jayant Bhatia
Modified: 2023-08-03 17:35 UTC (History)
6 users (show)

Fixed In Version: tfm-rubygem-katello-4.7.0.15-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-03 13:25:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36146 0 Normal Closed Need a better warning message for empty incremental export 2023-02-28 17:38:45 UTC
Red Hat Issue Tracker SAT-15983 0 None None None 2023-02-16 15:24:58 UTC
Red Hat Issue Tracker SAT-16172 0 None None None 2023-05-11 11:19:44 UTC
Red Hat Product Errata RHSA-2023:2097 0 None None None 2023-05-03 13:25:23 UTC

Description Jayant Bhatia 2023-02-14 21:11:08 UTC 
Description of problem:

Running "# hammer content-export incremental library --organization="RedHat"" command on Satellite server fails with below error.
~~~
Error: Error message: the server returns an error
HTTP status code: 400
Response headers: {"Date"=>"Tue, 14 Feb 2023 20:55:40 GMT", "Server"=>"gunicorn", "Content-Type"=>"application/json", "Vary"=>"Accept,Cookie", "Allow"=>"GET, POST, HEAD, OPTIONS", "X-Frame-Options"=>"DENY", "Content-Length"=>"136", "X-Content-Type-Options"=>"nosniff", "Referrer-Policy"=>"same-origin", "Correlation-ID"=>"b4463ab7-828a-4bf8-9839-eafcc3634cb0", "Access-Control-Expose-Headers"=>"Correlation-ID", "Via"=>"1.1 satellite.example.com", "Connection"=>"close"}
Response body: {"non_field_errors":["Incremental export can only be requested when there is a previous export or start_versions= has been specified."]}
undefined method `output_file_info' for nil:NilClass
~~~


Version-Release number of selected component (if applicable): satellite-6.13.0-4.el8sat.noarch


How reproducible: Always


Steps to Reproduce:

1. Run below command on Satellite to export the Library environment.

       # hammer content-export complete library --organization="My_Organization

2. The required directory is created within "/var/lib/pulp/exports/My_Organization/Export-Library"

3. Run following command to export Library environment incrementally:

       # hammer content-export incremental library --organization="My_Organization"


Actual results: The command fails with below error:

Error: Error message: the server returns an error
HTTP status code: 400
Response headers: {"Date"=>"Tue, 14 Feb 2023 20:55:40 GMT", "Server"=>"gunicorn", "Content-Type"=>"application/json", "Vary"=>"Accept,Cookie", "Allow"=>"GET, POST, HEAD, OPTIONS", "X-Frame-Options"=>"DENY", "Content-Length"=>"136", "X-Content-Type-Options"=>"nosniff", "Referrer-Policy"=>"same-origin", "Correlation-ID"=>"b4463ab7-828a-4bf8-9839-eafcc3634cb0", "Access-Control-Expose-Headers"=>"Correlation-ID", "Via"=>"1.1 dhcp131-67.gsslab.pnq2.redhat.com", "Connection"=>"close"}
Response body: {"non_field_errors":["Incremental export can only be requested when there is a previous export or start_versions= has been specified."]}
undefined method `output_file_info' for nil:NilClass


Expected results: The command should get executed successfully.


Additional info: Following steps as per Section-8.2 and Section-8.4 from following documentation: https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/managing_content/index?lb_target=preview

This issue is not observed on Satellite 6.12.
Comment 5 Partha Aji 2023-02-27 18:34:36 UTC 
Connecting redmine issue https://projects.theforeman.org/issues/36146 from this bug
Comment 7 Bryan Kearney 2023-02-27 20:03:37 UTC 
Upstream bug assigned to paji
Comment 8 Bryan Kearney 2023-02-27 20:03:39 UTC 
Upstream bug assigned to paji
Comment 9 Bryan Kearney 2023-02-27 20:03:49 UTC 
Upstream bug assigned to paji
Comment 10 Bryan Kearney 2023-02-27 20:03:51 UTC 
Upstream bug assigned to paji
Comment 22 errata-xmlrpc 2023-05-03 13:25:08 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.13 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-2023:2097
Note You need to log in before you can comment on or make changes to this bug.