Project

General

Profile

Bug #25011

Capsule upgrade failed at Upgrade Step: start_postgresql

Added by Evgeni Golov about 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1631943

Description of problem:
As services are now handled by foreman-maintain, capsule upgrade step: start_postgresql tried to start postgresql service using foreman-maintain.
But on capsule this service is not handled by f-m thus failed showing

Upgrade Step: start_postgresql...
out: Redirecting to 'foreman-maintain service'
out: Running Start Services
out: ================================================================================
out: Check if command is run as root user: [OK]
out: --------------------------------------------------------------------------------
out: Start applicable services: Starting the following service(s):
out: [FAIL]
out: No services found matching your parameters
out: --------------------------------------------------------------------------------
out: Scenario [Start Services] failed.
out:
out: The following steps ended up in failing state:
out:
out: [service-start]
out:
out: Resolve the failed steps and rerun
out: the command. In case the failures are false positives,
out: use --whitelist="service-start"
out:
out:
out: katello-service start --only postgresql failed! Check the output for error!
out: Upgrade step start_postgresql failed. Check logs for more information.

Version-Release number of selected component (if applicable):

Satellite 6.4 snap 23

How reproducible: always

Steps to Reproduce:
1. satellite-installer --scenario capsule --upgrade

Actual results: Upgrade failed at Upgrade Step: start_postgresql

Expected results: Successful upgrade.

Additional info:


Related issues

Has duplicate Foreman Maintain - Bug #24531: running upgrade procedure on smartproxy try to restart postgresqlDuplicate

Associated revisions

Revision 885f3e98 (diff)
Added by Evgeni Golov about 1 year ago

Fixes #25011 - only start PostgreSQL in the Katello scenario

There is no PostgreSQL required on the Proxy.

History

#1 Updated by The Foreman Bot about 1 year ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello-installer/pull/688 added

#2 Updated by Evgeni Golov about 1 year ago

  • Assignee changed from Anurag Patel to Evgeni Golov
  • Subject changed from Capsule upgrade failed at Upgrade Step: start_postgresql to Capsule upgrade failed at Upgrade Step: start_postgresql

#3 Updated by Evgeni Golov about 1 year ago

  • Status changed from Ready For Testing to Closed

#4 Updated by John Mitsch about 1 year ago

  • Triaged changed from No to Yes
  • Target version set to Katello 3.9.0

#5 Updated by John Mitsch about 1 year ago

  • Has duplicate Bug #24531: running upgrade procedure on smartproxy try to restart postgresql added

#6 Updated by Daniel Kimsey about 1 year ago

I ran into this issue during my 3.8.0 upgrade of my smart proxies.
Also discussed here: https://community.theforeman.org/t/katello-smart-proxy-upgrade-3-8-broken/11090/4

Also available in: Atom PDF