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.

Description of problem:
Satellite throws '500 Internal server errors' on importing a corrupted metadata template.

Version-Release number of selected component (if applicable):
Satellite 6.7 snap 6

How reproducible:
Always

Steps to Reproduce:
1. Create / Have the corrupted metadata template in local / git repo.
2. Attempt to import that template.

Actual results:
Satellite throws '500 Internal server errors' on importing a corrupted metadata template.

Expected results:
The satellite should show that the template cannot be imported due to 'corrupted metadata'.

Additional info:

In what way is metadata corrupted? Could you provide an example template please?

Unable to repro this for now, but let's keep this open for now. If I find it in testing in recent future, I can provide the details for the same.

Can we close now? It can be easily reopened in future if needed.

@Marek, Lets close this one for now.