Project

General

Profile

Actions

Bug #24531

closed

running upgrade procedure on smartproxy try to restart postgresql

Added by Anonymous over 5 years ago. Updated over 5 years ago.

Status:
Duplicate
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Following the upgrade procedure to version 3.8RC, the foreman-maintain is run and it tries to restart postgresql, while smartproxy don't have postgresql server running.

[root@foremanproxy01 ~]# foreman-installer --scenario foreman-proxy-content --upgrade --foreman-proxy-content-certs-tar foremanproxy01.tar --certs-update-all --certs-regenerate true --certs-deploy true
Resetting puppet server version param...
Marking certificate /root/ssl-build/foremanproxy01/foremanproxy01-apache for update
Marking certificate /root/ssl-build/foremanproxy01/foremanproxy01-foreman-client for update
Marking certificate /root/ssl-build/foremanproxy01/foremanproxy01-foreman-proxy for update
Marking certificate /root/ssl-build/foremanproxy01/foremanproxy01-foreman-proxy-client for update
Marking certificate /root/ssl-build/foremanproxy01/foremanproxy01-puppet-client for update
Marking certificate /root/ssl-build/foremanproxy01/foremanproxy01-qpid-broker for update
Marking certificate /root/ssl-build/foremanproxy01/foremanproxy01-qpid-client-cert for update
Marking certificate /root/ssl-build/foremanproxy01/foremanproxy01-qpid-router-client for update
Marking certificate /root/ssl-build/foremanproxy01/foremanproxy01-qpid-router-server for update
Upgrading, to monitor the progress on all related services, please do:
  foreman-tail | tee upgrade-$(date +%Y-%m-%d-%H%M).log
Upgrade Step: stop_services...
Redirecting to 'foreman-maintain service'
Running Stop Services
================================================================================
Check if command is run as root user:                                 [OK]
--------------------------------------------------------------------------------
Stop applicable services: Stopping the following service(s):

rh-mongodb34-mongod, squid, foreman-proxy, smart_proxy_dynflow_core, pulp_streamer, pulp_celerybeat, pulp_resource_manager, pulp_workers, puppetserver

/ All services stopped                                                [OK]      
--------------------------------------------------------------------------------

katello-service stop finished successfully!
Upgrade Step: start_postgresql...
Redirecting to 'foreman-maintain service'
Running Start Services
================================================================================
Check if command is run as root user:                                 [OK]
--------------------------------------------------------------------------------
Start applicable services: Starting the following service(s):
                                   [FAIL]
No services found matching your parameters
--------------------------------------------------------------------------------
Scenario [Start Services] failed.

The following steps ended up in failing state:

  [service-start]

Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="service-start" 

katello-service start --only postgresql failed! Check the output for error!
Upgrade step start_postgresql failed. Check logs for more information.

Related issues 1 (0 open1 closed)

Is duplicate of Katello - Bug #25011: Capsule upgrade failed at Upgrade Step: start_postgresqlClosedEvgeni GolovActions
Actions #1

Updated by Anonymous over 5 years ago

removing the "--upgrade" allowed the command to finish, but I dont know yet if there will be consequences of this bypass.

Actions #2

Updated by John Mitsch over 5 years ago

  • Project changed from Katello to Foreman Maintain
Actions #3

Updated by Anthony Chevalet over 5 years ago

  • Priority changed from Normal to High

Raising to high as it is blocking proxy upgrade to 3.8.0

Actions #4

Updated by John Mitsch over 5 years ago

This was fixed, I'm struggling to find the issue to mark as a duplicate, but will keep looking!

Actions #5

Updated by John Mitsch over 5 years ago

  • Is duplicate of Bug #25011: Capsule upgrade failed at Upgrade Step: start_postgresql added
Actions #6

Updated by John Mitsch over 5 years ago

  • Status changed from New to Duplicate
Actions #7

Updated by Anthony Chevalet over 5 years ago

Thanks!

Actions

Also available in: Atom PDF