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.

When upgrade fails during our pre/post steps (usually rake tasks), there is no way to recover other than manually investigating what happened.

This is a suggestion to store list of successful steps so upgrade can be either reexecuted (if the rest is idempotent) or at least providing an option to skip executed steps.

Easy implementation would be touching some timestamp files in /var/lib and informing user about skipped steps (and how to re-execute them when needed).

This is a RFE but I think this should be handled with priority for the next major upgrade.

We are already doing the touching thing. How does it differ form https://bugzilla.redhat.com/show_bug.cgi?id=1264597 ?

I though the upgrades are idempotent.

-- Ivan

Sure.