This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2172937 - You can export but not import 'Default Organization View' as Content View
Summary: You can export but not import 'Default Organization View' as Content View
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Inter Satellite Sync
Version: 6.10.7
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-23 14:44 UTC by Stephen Wadeley
Modified: 2024-10-05 04:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 16:09:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-25054 0 None Migrated None 2024-06-06 16:09:00 UTC

Description Stephen Wadeley 2023-02-23 14:44:41 UTC 
Description of problem:

You can export but not import 'Default Organization View' as Content View

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


How reproducible:
Every time


Steps to Reproduce:
 ~]# hammer content-export complete version \
> --content-view="Default Organization View" \
> --version=1.0 \
> --organization="Default Organization"
 
then I moved it to /var/lib/pulp/imports/
 
this fails
 ~]# date &&  hammer content-import version --organization="Default Organization" --path=/var/lib/pulp/imports/2023-02-23T02-32-50-05-00
Thu Feb 23 06:04:16 EST 2023
Could not import the archive.:
  Unable to import in to Content View specified in the metadata - 'Default Organization View'. The 'import_only' attribute for the content view is set to false. To mark this Content View as importable, have your system administrator run the following command on the server.
  foreman-rake katello:set_content_view_import_only ID=1

Actual results:

running `foreman-rake katello:set_content_view_import_only ID=1` does  not solve the problem

Expected results:

Either I cannot export "Default Organization View" as a Content View or I can import it.
No point to allow an export if import does not work.


Additional info:
I was told exporting should not be allowed.

I am setting severity to medium because although it seems trivial it does waste a lot of time.
Comment 1 Partha Aji 2023-04-27 15:40:11 UTC 
You are right. We should not allow one to export the default organization view.
Comment 2 Brad Buckingham 2024-03-21 21:07:37 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 4 Brad Buckingham 2024-05-10 13:15:28 UTC 
Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional discussion; however, it may be closed in a future iteration.
Comment 6 Eric Helms 2024-06-06 16:09:01 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 7 Red Hat Bugzilla 2024-10-05 04:25:50 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.