Project

General

Profile

Actions
Copy link

Bug #33488

closed

Restore doesn't wipe qpidd journal for qpidd 1.39

Added by Evgeni Golov over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Evgeni Golov
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman_maintain/pull/535
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Ohai,

in #28462 we introduced a step to the restore, that wipes parts of the qpidd journal on restore, as it sometimes blocks qpidd from starting up properly again.

Somewhere between qpid-cpp-server-1.36.0-28.el7amq.x86_64 (Satellite) and qpid-cpp-server-1.39.0-1.el7.x86_64 (Katello upstream/EPEL), the on-disk path of the files changed from /var/lib/qpidd/.qpidd/ to /var/lib/qpidd/.

This results in upstream restores sometimes failing to start up qpidd.

Let's support both paths!

Related issues 1 (0 open — 1 closed)

Related to Foreman Maintain - Bug #28462: Cloning a Satellite with out pulp data fails to start qpid during restoreClosedChris RobertsActions
Actions
Copy link
 #1

Updated by Evgeni Golov over 2 years ago

  • Related to Bug #28462: Cloning a Satellite with out pulp data fails to start qpid during restore added
Actions
Copy link
 #2

Updated by The Foreman Bot over 2 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_maintain/pull/535 added
Actions
Copy link
 #3

Updated by Evgeni Golov over 2 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link

Also available in: Atom PDF