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.
DescriptionJustin Sherrill
2011-10-26 15:15:23 UTC
If a promotion fails for some reason, we leave the changeset in a 'promoting' state. Since it has failed though, delayed jobs will not attempt it again, and you can no longer promote any other changesets. It must be deleted and there is no indication of what went wrong.
Ideally a promotion would never fail, but it does happen on occasion and we need to at least try to handle it.
Added new state 'failed' that is set when any exception raises during a promotion. The exception message is saved in changeset's async task status.
commit 8681c878900ab4dab19b7a69fd2317a4a1a79a38
Author: Tomas Strachota <tstrachota>
Date: Mon Nov 14 19:11:55 2011 +0100
749258 - new state 'failed' for changesets
Repro steps I can think of could be:
- create a product with a repo and promote it
- create a new changeset and add only the repo
- delete the repo
- try to promote the changeset
- check the changeset's status
Hey Garik! I happened to be working on this area today, and after checking with Tomas, I believe we can close it as validated. Basically, the original issue prevented you from doing anything else via the web ui. Now, one can delete the failed changeset, set it on review and make changes, promote it again, or add a new changeset. Since you got the issue assigned to you I won't close it until you've had a chance to look at it. :)