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.
Description of problem:
If an error occurs during a manifest upload, an error message appears along with a "successful" message.
Version-Release number of selected component (if applicable):
CloudForms 1.1 beta
How reproducible:
Every time
Steps to Reproduce:
1. Upload manifest
2. During upload, cause an error
3. View results
Actual results:
Incorrect message along with correct message
Expected results:
Consistent messages
Additional info:
Yes, this is a priority to fix.
A newer version of candlepin will report the deletion of the manifest which will clear up a little of the confusion. The ideal fix is not to just show candlepin history here, but to show katello generated messages as well (or in place of).
*** This bug has been marked as a duplicate of bug 855461 ***