Bug 2122090

Summary:	Syncable exports not properly validated
Product:	Red Hat Satellite	Reporter:	Partha Aji <paji>
Component:	Inter Satellite Sync	Assignee:	Partha Aji <paji>
Status:	CLOSED ERRATA	QA Contact:	Radek Mynar <rmynar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.11.2	CC:	chrobert, pcreech
Target Milestone:	6.12.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-katello-4.5.0.7-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-16 13:35:34 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 Partha Aji 2022-08-29 05:06:04 UTC

Description of problem:
Syncable exports are only available for yum and file repos. However the code tries to syncably export ansible repos also.

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

How reproducible:
always

Steps to Reproduce:
1. Create and sync an ansible repo
2. Export the ansible repo syncably via the following command `hammer content-export complete repository --id=<ansible id> --format=syncable`

Actual results:
Misleading error along "This repo is not marked immediate and hence cant be exported"


Expected results:
Cannot Sync Ansible. Only yum or file is available


Additional info:
On a library export or a content view with a yum, file, ansible repositories the syncable export complains the same and ignores files and ansible.
We'd like it to ignore ansible with a better message but export file and yum.

Comment 1 Partha Aji 2022-08-29 05:08:41 UTC

Connecting redmine issue https://projects.theforeman.org/issues/35442 from this bug

Comment 2 Bryan Kearney 2022-08-29 08:05:31 UTC

Upstream bug assigned to paji

Comment 3 Bryan Kearney 2022-08-29 08:05:33 UTC

Upstream bug assigned to paji

Comment 4 Bryan Kearney 2022-09-03 00:04:58 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35442 has been resolved.

Comment 6 Chris Roberts 2022-10-10 17:47:26 UTC

VERFIED,

ACK works great

```bash
[root@centos8-stream-katello-nightly ~]# hammer content-export complete repository --id=4 --format=syncable
Could not export the repository:
  500 Internal Server Error
2022-09-01T15:00:57 [E|app|c4392060] RuntimeError: NOTE: Unable to export repository 'Ansible' because it does not have an exportable content type.
```

```bash
[root@centos8-stream-katello-nightly ~]# hammer content-export complete library --organization-id=1 --format=syncable
[...............................................................................................................................................................] [100%]
Generated /var/lib/pulp/exports/Default_Organization/Export-Library-SYNCABLE/1.0/2022-09-01T15-02-48-00-00
```

Comment 10 errata-xmlrpc 2022-11-16 13:35:34 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.12 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-2022:8506