Bug 1354631
| Summary: | Users should be warned during upgrade of long running Pulp migrations | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Eric Helms <ehelms> | ||||||
| Component: | Pulp | Assignee: | satellite6-bugs <satellite6-bugs> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Sachin Ghai <sghai> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.2.0 | CC: | bbuckingham, bmbouter, cwelton, daviddavis, dkliban, ehelms, ggainey, ipanova, mhrivnak, pcreech, rchan, riehecky, sghai, ttereshc | ||||||
| Target Milestone: | Unspecified | Keywords: | Triaged | ||||||
| Target Release: | Unused | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | katello-installer-base-3.0.0.52-1 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-07-27 11:37:26 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Eric Helms
2016-07-11 19:29:21 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug. The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug. Created redmine issue http://projects.theforeman.org/issues/15660 from this bug I'm assuming these warning should appear on console as well as in log files. right ? If so, I can see them only in logs but not on console: like in /var/log/messages: Jul 14 08:14:36 qe-sat6-upgrade-rhel7 pulp: pulp.server.db.manage:INFO: Applying pulp_puppet.plugins.migrations version 4 Jul 14 08:14:36 qe-sat6-upgrade-rhel7 pulp: pulp_puppet.plugins.migrations.0004_standard_storage_path:INFO: **************************************************************************************** Jul 14 08:14:36 qe-sat6-upgrade-rhel7 pulp: pulp_puppet.plugins.migrations.0004_standard_storage_path:INFO: * NOTE: This migration may take a long time depending on the size of your Pulp content * Jul 14 08:14:36 qe-sat6-upgrade-rhel7 pulp: pulp_puppet.plugins.migrations.0004_standard_storage_path:INFO: **************************************************************************************** Jul 14 08:15:05 qe-sat6-upgrade-rhel7 pulp: pulp.server.db.manage:INFO: Migration to pulp_puppet.plugins.migrations version 4 complete. console is showing logs like: ~]# satellite-installer --scenario satellite --upgrade Upgrading... Upgrade Step: stop_services... Redirecting to /bin/systemctl stop httpd.service Redirecting to /bin/systemctl stop pulp_workers.service Redirecting to /bin/systemctl stop pulp_resource_manager.service Redirecting to /bin/systemctl stop pulp_celerybeat.service Redirecting to /bin/systemctl stop foreman-proxy.service Redirecting to /bin/systemctl stop tomcat.service Redirecting to /bin/systemctl stop qdrouterd.service Redirecting to /bin/systemctl stop qpidd.service Success! Upgrade Step: start_databases... Redirecting to /bin/systemctl start mongod.service Redirecting to /bin/systemctl start postgresql.service Success! Upgrade Step: update_http_conf... Upgrade Step: migrate_pulp... 26559 You should be seeing them in the installer logs as well as the console output. Created attachment 1179872 [details]
I don't see long migration warnings on console..
Sachin, The logs appear to indicate you had already ran an update on this machine? The output of the messages indicating from Pulp that a particular migration will take a long time can only be seen when those migrations are run. Not every migration can take a long time, so they are coded to a few specific migrations. Thus I would only expect to see the message during the initial Sat 6.1 to 6.2 migration in the Pulp migration output. Therefore, I am going to move this back to MODIFIED and then to ON_QA when https://bugzilla.redhat.com/show_bug.cgi?id=1356447 is pushed to ON_QA. Eric, Thanks for the info. But I didn't run the update twice. This is the machine where I applied the fix given in bz1356447 before performing upgrade. And I don't see long migration warnings on console during first run. I'll see how this goes with next snap. thanks. Verified with upgrade from Sat6.1.9 -> sat6.2 GA snap20.2 I can see warnings for long running pulp migrations on console as well as in logs. Please see screenshot for verification. Created attachment 1181009 [details]
long migration warnings on console
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug. 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/RHBA-2016:1501 |