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.
Created attachment 635046[details]
screenshot showing error notification and success message in Upload History
Description of problem:
I really don't know how easily this will be reproduced in the future or how valid it is outside a very narrow corner case. But it's worth looking into.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Upload a manifest that (for whatever reason) is rejected on the CDN side.
2. Observe ensuing error message; observe Upload History message
Actual results:
User gets error notification but Upload History message box indicates succes.
Expected results:
Should fail on both fronts, probably.
Additional info:
See attached screenshot.
The manifest import comes from candlepin only, unfortunately, and this error comes from pulp. What is happening is that candlepin imports successfully, then pulp fails, and candlepin then deletes the manifest. Newer versions of candlepin (7.16+) will show the deleted message.
This bug was closed because of a lack of activity. If you feel this bug should be reconsidered for attention please feel free to re-open the bug with a comment stating why it should be reconsidered.
Created attachment 635046 [details] screenshot showing error notification and success message in Upload History Description of problem: I really don't know how easily this will be reproduced in the future or how valid it is outside a very narrow corner case. But it's worth looking into. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Upload a manifest that (for whatever reason) is rejected on the CDN side. 2. Observe ensuing error message; observe Upload History message Actual results: User gets error notification but Upload History message box indicates succes. Expected results: Should fail on both fronts, probably. Additional info: See attached screenshot.