Bug 1967685
| Summary: | After upgrade, some of the satellite services failed to start | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Devendra Singh <desingh> |
| Component: | Satellite Maintain | Assignee: | Justin Sherrill <jsherril> |
| Status: | CLOSED ERRATA | QA Contact: | Devendra Singh <desingh> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.10.0 | CC: | apatel, aupadhye, egolov, ekohlvan, gtalreja, jsherril, kgaikwad, osousa, wclark |
| Target Milestone: | 6.10.0 | Keywords: | AutomationBlocker, Regression, Triaged, Upgrades |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | rubygem-foreman_maintain-0.8.3 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-16 13:48:05 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: | |||
|
Description
Devendra Singh
2021-06-03 15:22:51 UTC
`Following services are not running: pulp_celerybeat, pulp_resource_manager, smart_proxy_dynflow_core` These services are removed in Satellite 6.10, so the fix should be to remove them from foreman-maintain Are you sure that the satellite actually upgraded to 6.10? I tried this and ran into a ton of dependency errors (https://bugzilla.redhat.com/show_bug.cgi?id=1972995). Looking at your output, i don't see packages getting updated or the installer run, was your output just part of it? (In reply to Justin Sherrill from comment #9) > Are you sure that the satellite actually upgraded to 6.10? I tried this and > ran into a ton of dependency errors > (https://bugzilla.redhat.com/show_bug.cgi?id=1972995). Looking at your > output, i don't see packages getting updated or the installer run, was your > output just part of it? This problem was happened on 6.10 Snap3, on 6.10 snap5 upgrade gets failed due to a package dependency issue. Devendra, did you see amit's question: Devendra can you please confirm if you run : foreman-maintain service restart explicitly after the upgrade do you see pulp2 services getting restarted? and its specifically happening in the upgrade run's post actions? I kind of reproduced this and kind of didnt' reproduce this: SNIP Upgrade Step 3/5: katello:upgrades:4.0:remove_ostree_puppet_content. ============================================= Upgrade Step 4/5: katello:upgrades:4.1:sync_noarch_content. ============================================= Upgrade Step 5/5: katello:upgrades:4.1:fix_invalid_pools. I, [2021-06-23T21:46:57.541313 #21212] INFO -- : Corrected 0 invalid pools I, [2021-06-23T21:46:57.541350 #21212] INFO -- : Removed 0 orphaned pools Success! * Satellite is running at https://610upgradetest.windhelm.example.com * To install an additional Capsule on separate machine continue by running: capsule-certs-generate --foreman-proxy-fqdn "$CAPSULE" --certs-tar "/root/$CAPSULE-certs.tar" * Capsule is running at https://610upgradetest.windhelm.example.com:9090 The full log is at /var/log/foreman-installer/satellite.log Package versions are being locked. [OK] -------------------------------------------------------------------------------- Execute upgrade:run rake task: [OK] -------------------------------------------------------------------------------- Running Procedures after migrating to Satellite 6.10 ================================================================================ Start applicable services: Starting the following service(s): rh-mongodb34-mongod, postgresql, rh-redis5-redis, squid, pulp_celerybeat, pulp_resource_manager, pulp_streamer, pulp_workers, tomcat, dynflow-sidekiq@orchestrator, foreman, httpd, puppetserver, dynflow-sidekiq@worker-1, dynflow-sidekiq@worker-hosts-queue-1, foreman-proxy - starting squid Warning: postgresql.service changed on disk. Run 'systemctl daemon-reload' to reload units. \ All services started [OK] -------------------------------------------------------------------------------- re-enable sync plans: | Total 0 sync plans are now enabled. [OK] -------------------------------------------------------------------------------- Remove maintenance_mode chain from iptables: [OK] -------------------------------------------------------------------------------- SNIP So i didn't see a failure, but the pulp2 services were started. running foreman-maintain restart did not start them, so i think you're right amit, we need to 're-running' the feature detection after the installer runs? Also to clarify, even though i didn't get an error, pulp2 services were spewing errors in the logs, so this still needs to be handled. Connecting redmine issue https://projects.theforeman.org/issues/32870 from this bug (In reply to Justin Sherrill from comment #11) > Devendra, did you see amit's question: > > > Devendra can you please confirm if you run : foreman-maintain service > restart explicitly after the upgrade do you see pulp2 services getting > restarted? and its specifically happening in the upgrade run's post actions? Sorry I missed, yes after the upgrade all the satellite services were running, I restarted the services via foreman-maintain and it worked but not sure about pulp2 or pulp3. Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32870 has been resolved. Verified on 6.10 Snap9 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 (Satellite 6.10 Satellite Maintenance Release), 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-2021:4697 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |