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

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 2271431

Summary:	Incremental export of Library in regular format is not possible after a syncable full export in Red Hat Satellite 6
Product:	Red Hat Satellite	Reporter:	soham <smajumda>
Component:	Inter Satellite Sync	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.14.2	CC:	ahumbe, ashipati, dalley, iballou, paji, rlavi, saydas
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA
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-06-06 17:26:54 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 soham 2024-03-25 16:11:05 UTC

Description of problem:
Incremental export of Library in regular format is not possible after a syncable full export in Red Hat Satellite 6

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


How reproducible:


[root@vm207-21 imports]# hammer content-export complete library --organization="RedHat" --format=syncable
[..........................................................................................................................................................................................................] [100%]
Generated /var/lib/pulp/exports/RedHat/Export-Library-SYNCABLE/2.0/2024-03-25T20-52-41-05-30/metadata.json




[root@vm207-21 imports]# hammer content-export incremental library --organization="RedHat"
Could not export the library:
  Unable to incrementally export. Do a Full Export on the library content before updating from the latest increment.




But the same thing works for a Content view:


[root@breakfix1-sat ~]# hammer content-export complete version \
> --content-view="cv3" \
> --version=1.0 \
> --organization="RedHat" \
> --format=syncable
[..........................................................................................................................................................................................................] [100%]
Generated /var/lib/pulp/exports/RedHat/cv3/1.0/2024-03-25T20-03-37-05-30/metadata.json




# hammer content-export incremental version \
> --content-view="cv3" \
> --organization="RedHat" \
> --version=2.0
[..........................................................................................................................................................................................................] [100%]

Comment 5 Sayan Das 2024-04-26 15:00:00 UTC

I am on 6.14.3 and this is not reproducible there:

# rpm -q satellite katello foreman
satellite-6.14.3-1.el8sat.noarch
katello-4.9.0-1.el8sat.noarch
foreman-3.7.0.11-2.el8sat.noarch

[root@satellite614 reproducer]# hammer content-export complete library --organization="ACME" --format=syncable
[..............................................................................................................................................................................................................................] [100%]
Generated /var/lib/pulp/exports/ACME/Export-Library-SYNCABLE/2.0/2024-04-26T20-24-37-05-30/metadata.json


[root@satellite614 reproducer]# hammer content-export incremental library --organization="ACME" 
[..............................................................................................................................................................................................................................] [100%]
Generated /var/lib/pulp/exports/ACME/Export-Library/2.0/2024-04-26T20-25-30-05-30/metadata.json


And i verified the opposite as well i.e. doing the complete export via the importable method and doing the incremental via syncable. Even that works fine.

I tried using the collection redhat.satellite 3.14.0 as well and that works fine as well. 

@soham if you upgrade your 6.14.2 to 6.14.3, Do you still see the same issue ?

Comment 6 Sayan Das 2024-04-26 16:44:29 UTC

Ok.. It seems something odd is going on. 

# hammer content-export complete library --organization="ACME" --format=syncable
[..............................................................................................................................................................................................................................] [100%]
Generated /var/lib/pulp/exports/ACME/Export-Library-SYNCABLE/2.0/2024-04-26T20-24-37-05-30/metadata.json


# hammer content-export incremental library --organization="ACME" 
[..............................................................................................................................................................................................................................] [100%]
Generated /var/lib/pulp/exports/ACME/Export-Library/2.0/2024-04-26T20-25-30-05-30/metadata.json


# hammer content-export incremental library --organization="ACME" --format=syncable
[..............................................................................................................................................................................................................................] [100%]
Generated /var/lib/pulp/exports/ACME/Export-Library-SYNCABLE/3.0/2024-04-26T20-41-11-05-30/metadata.json

# hammer content-export incremental library --organization="ACME" --format=importable
[..............................................................................................................................................................................................................................] [100%]
Generated /var/lib/pulp/exports/ACME/Export-Library/3.0/2024-04-26T20-41-28-05-30/metadata.json

--> Here i enabled and synced a new repo in satellite

# hammer content-export incremental library --organization="ACME" --format=syncable
[..............................................................................................................................................................................................................................] [100%]
Generated /var/lib/pulp/exports/ACME/Export-Library-SYNCABLE/4.0/2024-04-26T21-51-53-05-30/metadata.json


and i could see the repo contents inside /var/lib/pulp/exports/ACME/Export-Library-SYNCABLE/4.0/2024-04-26T21-51-53-05-30/ as well. 



Now, Developers tested on a fresh 6.15.0 and My colleague Soham tested on a fresh 6.14.3 , they run into the same error as reported in Description of the BUG. 


The only difference between their and mine setup is that, Before these attempts, I did several full and incremental exports of Library , with the --destination-server flag and that is in the export history as well. 

So perhaps, it's about some sort of sequence or pattern in which this would work but normally, in a fresh satellite, It will always fail.

Comment 8 Sayan Das 2024-05-14 16:30:09 UTC

Ok.. Assuming this behavior is indeed reproducible, I wanted to ask whether it's a valid workflow or not i.e. having done the complete export as syncable and then trying to do the incremental as importable or vice-versa ?

Comment 9 Eric Helms 2024-06-06 17:26:54 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Comment 10 Red Hat Bugzilla 2024-10-05 04:27:29 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days