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.
Bug 1382502 - Provide more information about currently running upgrade steps
Summary: Provide more information about currently running upgrade steps
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Upgrades
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Martin Bacovsky
QA Contact: Nikhil Kathole
URL:
Whiteboard:
Depends On:
Blocks: Sat6_Upgrades
TreeView+ depends on / blocked
 
Reported: 2016-10-06 20:19 UTC by Ivan Necas
Modified: 2019-09-26 15:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 17192 0 None None None 2016-11-02 23:08:03 UTC

Description Ivan Necas 2016-10-06 20:19:26 UTC 
Description of problem:

Currently, when the upgrade is happening, the pre-upgrade/post-upgrade
steps don't provide the output as they are running, but rather just
show it after the step is finished. Since some of the upgrade tasks
can take quite a long time, it's very inconvenient to not produce
any output in the meant time, and it's hard to the user to tell
if it's stuck or actually doing something

Steps to Reproduce:
1. run upgrade on reasonably large satellite (so that the upgrade takes some time)
2. see some tasks performing over tens of minutes

Actual results:

The screen is unchanged for several minutes, making it
hard to tell if it's performing something, or just hang

Expected results:

The installer updates frequently about what's going on right now, but
passing the upgrade script output to the user at it runs (it also expects the
upgrade step producing reasonable output during the execution)
Comment 2 Ivan Necas 2016-11-02 23:08:01 UTC 
Created redmine issue http://projects.theforeman.org/issues/17192 from this bug
Comment 3 Satellite Program 2017-01-30 19:00:35 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17192 has been resolved.
Comment 4 Nikhil Kathole 2017-12-20 13:12:29 UTC 
VERIFIED

Performed upgrade 6.2 to 6.3 snap 29, upgrade steps explain what is going on when upgrade is in the progress. 

Upgrade Step: migrate_foreman...
API controllers newer than Apipie cache! Run apipie:cache rake task to regenerate cache.
== 20151210143537 AddTypeToMailNotification: migrating ========================
-- add_column(:mail_notifications, :type, :string, {:limit=>255})
   -> 0.0006s
== 20151210143537 AddTypeToMailNotification: migrated (0.0195s) ===============

== 20160203110216 AddDefaultValueForBookmarkPublicField: migrating ============
-- change_column(:bookmarks, :public, :boolean, {:default=>false, :null=>false})
   -> 0.0020s
== 20160203110216 AddDefaultValueForBookmarkPublicField: migrated (0.0042s) ===

== 20160225115638 RemoveDefaultUserRole: migrating ============================
== 20160225115638 RemoveDefaultUserRole: migrated (0.0949s) ===================

== 20160225131917 RenameAnonymousRole: migrating ==============================
== 20160225131917 RenameAnonymousRole: migrated (0.0012s) =====================

== 20160228140111 UpdateParamsPriority: migrating =============================
== 20160228140111 UpdateParamsPriority: migrated (0.0091s) ====================

== 20160308102459 RemovePermissionsFromRoles: migrating =======================
-- remove_column(:roles, :permissions)
   -> 0.0004s
== 20160308102459 RemovePermissionsFromRoles: migrated (0.0004s) ==============

== 20160315161936 AddEncryptedToSettings: migrating ===========================
-- add_column(:settings, :encrypted, :boolean, {:null=>false, :default=>false})
   -> 0.0067s
== 20160315161936 AddEncryptedToSettings: migrated (0.0067s) ==================
Comment 6 Satellite Program 2018-02-21 16:54:37 UTC 
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> > 
> > For information on the advisory, and where to find the updated files, follow the link below.
> > 
> > If the solution does not work for you, open a new bug report.
> > 
> > https://access.redhat.com/errata/RHSA-2018:0336
Note You need to log in before you can comment on or make changes to this bug.