2124215 – During customer backup restore installer fails with qpidd.service start-post operation timed out. Stopping.

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 2124215 - During customer backup restore installer fails with qpidd.service start-post operation timed out. Stopping.

Summary: During customer backup restore installer fails with qpidd.service start-post ...

Keywords:
Status:	CLOSED WONTFIX
Alias:	None
Product:	Red Hat Satellite
Classification:	Red Hat
Component:	Upgrades
Sub Component:
Version:	6.10.7
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	high
Target Milestone:	Unspecified
Assignee:	satellite6-bugs
QA Contact:	Lukas Pramuk
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2022-09-05 10:01 UTC by Lukas Pramuk
Modified:	2023-01-17 18:32 UTC (History)
CC List:	6 users (show)
Fixed In Version:
Doc Type:	Known Issue
Doc Text:
Clone Of:
Environment:
Last Closed:	2023-01-17 18:32:32 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	SAT-12798	0	None	None	None	2022-09-07 15:24:42 UTC
Red Hat Knowledge Base (Solution)	6983249	0	None	None	None	2022-11-02 15:48:57 UTC

Description Lukas Pramuk 2022-09-05 10:01:36 UTC

Description of problem:
During customer DB restore installer fails with: 
qpidd.service start-post operation timed out. Stopping.


Version-Release number of selected component (if applicable):
6.10.7 (backup is older 6.10.z)

How reproducible:
deterministic with the backup

Steps to Reproduce:
1. Restore using satellite-clone 
# satellite-clone -y
...
TASK [satellite-clone : restore using foreman-maintain] ************************
Sunday 04 September 2022  20:17:19 -0400 (0:00:00.699)       0:27:37.141 ****** 
fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["foreman-maintain", "restore", "--assumeyes", "/tmp/backup"], "delta": "0:20:18.813265", "end": "2022-09-04 20:37:38.924989", "msg": "non-zero return code", "rc": 1, "start": "2022-09-04 20:17:20.111724", "stderr": "", "stderr_lines": [], "stdout":
---
Running Restore backup
================================================================================
Check if command is run as root user:                                 [OK]
--------------------------------------------------------------------------------
Validate backup has appropriate files:                                [OK]
--------------------------------------------------------------------------------
Confirm dropping databases and running restore: 

WARNING: This script will drop and restore your database.
Your existing installation will be replaced with the backup database.
Once this operation is complete there is no going back.
Do you want to proceed? (assuming yes)
                                                                      [OK]      
--------------------------------------------------------------------------------
Validate hostname is the same as backup:                              [OK]
--------------------------------------------------------------------------------
Setting file security: 
/ Restoring SELinux context                                           [OK]      
--------------------------------------------------------------------------------
Restore configs from backup: 
- Restoring configs                                                   [OK]      
--------------------------------------------------------------------------------
Run installer reset: 
\ Installer reset                                                     [FAIL]    
Failed executing yes | satellite-installer -v --reset-data --disable-system-checks , exit status 6:
 2022-09-03 06:18:43 [NOTICE] [root] Loading installer configuration. This will take some time.
2022-09-03 06:18:48 [NOTICE] [root] Running installer with log based terminal output at level NOTICE.
2022-09-03 06:18:48 [NOTICE] [root] Use -l to set the terminal output log level to ERROR, WARN, NOTICE, INFO, or DEBUG. See --full-help for definitions.
Are you sure you want to continue? This will drop the databases, reset all configurations that you have made and bring all application data back to a fresh install. [y/n]
Package versions are locked. Continuing with unlock.
2022-09-03 06:20:30 [NOTICE] [pre] Dropping foreman database!
2022-09-03 06:20:30 [NOTICE] [pre] Dropping candlepin database!
2022-09-03 06:20:30 [NOTICE] [pre] Dropping pulpcore database!
2022-09-03 06:20:30 [WARN  ] [pre] Pulpcore content directory not present at '/var/lib/pulp/docroot'
2022-09-03 06:20:30 [WARN  ] [pre] Skipping system checks.
2022-09-03 06:20:30 [WARN  ] [pre] Skipping system checks.
2022-09-03 06:20:36 [NOTICE] [configure] Starting system configuration.
2022-09-03 06:20:50 [NOTICE] [configure] 250 configuration steps out of 2125 steps complete.
2022-09-03 06:21:28 [NOTICE] [configure] 500 configuration steps out of 2125 steps complete.
2022-09-03 06:21:28 [NOTICE] [configure] 750 configuration steps out of 2127 steps complete.
2022-09-03 06:21:38 [NOTICE] [configure] 1000 configuration steps out of 2132 steps complete.
2022-09-03 06:21:38 [NOTICE] [configure] 1250 configuration steps out of 2136 steps complete.
2022-09-03 06:23:09 [ERROR ] [configure] Systemd start for qpidd failed!
2022-09-03 06:23:09 [ERROR ] [configure] journalctl log for qpidd:
2022-09-03 06:23:09 [ERROR ] [configure] -- Logs begin at Sat 2022-09-03 05:46:46 EDT, end at Sat 2022-09-03 06:23:09 EDT. --
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:19:00 sat.local systemd[1]: Stopping An AMQP message broker daemon....
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:20:30 sat.local systemd[1]: qpidd.service stop-sigterm timed out. Killing.
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:20:30 sat.local systemd[1]: qpidd.service: main process exited, code=killed, status=9/KILL
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:20:30 sat.local systemd[1]: Stopped An AMQP message broker daemon..
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:20:30 sat.local systemd[1]: Unit qpidd.service entered failed state.
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:20:30 sat.local systemd[1]: qpidd.service failed.
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:21:39 sat.local systemd[1]: Starting An AMQP message broker daemon....
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:23:09 sat.local systemd[1]: qpidd.service start-post operation timed out. Stopping.
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:23:09 sat.local systemd[1]: Failed to start An AMQP message broker daemon..
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:23:09 sat.local systemd[1]: Unit qpidd.service entered failed state.
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:23:09 sat.local systemd[1]: qpidd.service failed.
2022-09-03 06:23:09 [ERROR ] [configure] /Stage[main]/Qpid::Service/Service[qpidd]/ensure: change from 'stopped' to 'running' failed: Systemd start for qpidd failed!
2022-09-03 06:23:09 [ERROR ] [configure] journalctl log for qpidd:
2022-09-03 06:23:09 [ERROR ] [configure] -- Logs begin at Sat 2022-09-03 05:46:46 EDT, end at Sat 2022-09-03 06:23:09 EDT. --
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:19:00 sat.local systemd[1]: Stopping An AMQP message broker daemon....
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:20:30 sat.local systemd[1]: qpidd.service stop-sigterm timed out. Killing.
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:20:30 sat.local systemd[1]: qpidd.service: main process exited, code=killed, status=9/KILL
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:20:30 sat.local systemd[1]: Stopped An AMQP message broker daemon..
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:20:30 sat.local systemd[1]: Unit qpidd.service entered failed state.
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:20:30 sat.local systemd[1]: qpidd.service failed.
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:21:39 sat.local systemd[1]: Starting An AMQP message broker daemon....
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:23:09 sat.local systemd[1]: qpidd.service start-post operation timed out. Stopping.
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:23:09 sat.local systemd[1]: Failed to start An AMQP message broker daemon..
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:23:09 sat.local systemd[1]: Unit qpidd.service entered failed state.
2022-09-03 06:23:09 [ERROR ] [configure] Sep 03 06:23:09 sat.local systemd[1]: qpidd.service failed.
2022-09-03 06:25:57 [NOTICE] [configure] 1500 configuration steps out of 2137 steps complete.
2022-09-03 06:35:16 [NOTICE] [configure] 1750 configuration steps out of 2137 steps complete.
2022-09-03 06:36:35 [NOTICE] [configure] 2000 configuration steps out of 2137 steps complete.
2022-09-03 06:37:55 [NOTICE] [configure] System configuration has finished.

  There were errors detected during install.
  Please address the errors and re-run the installer to ensure the system is properly configured.
  Failing to do so is likely to result in broken functionality.

  The full log is at /var/log/foreman-installer/satellite.log
Package versions are being locked.
--------------------------------------------------------------------------------
Scenario [Restore backup] failed.

The following steps ended up in failing state:

  [restore-installer-reset]


Actual results:
restore fails for this backup

Expected results:
restore succeeds for this backup

Comment 15 Malhar Jivrajani 2022-11-16 14:47:23 UTC

Link to the updated document: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html-single/release_notes/index#ref_known-issues_assembly_introducing-red-hat-satellite

Comment 16 Eric Helms 2023-01-17 18:32:32 UTC

As we are unable to reliably produce this, and it appears related to the load on the system causing a one off race condition. Given the fix is simple, and this is an outlier bug I am opting to close it for now.

Note You need to log in before you can comment on or make changes to this bug.