Bug 1161556 - Disaster recovery documentation mentions non-existing service pulp-server
Summary: Disaster recovery documentation mentions non-existing service pulp-server
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Deadline: 2015-04-03
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs User Guide
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: David O'Brien
QA Contact: Peter Ondrejka
URL:
Whiteboard:
: 1195126 (view as bug list)
Depends On:
Blocks: 1179535 Sat6_HA_Tracker
TreeView+ depends on / blocked
 
Reported: 2014-11-07 10:53 UTC by Johan Swensson
Modified: 2019-09-26 16:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-03 07:16:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Johan Swensson 2014-11-07 10:53:05 UTC 
Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html/User_Guide/sect-Disaster_Recovery.html

Section Number and Name: Option Two: Offline Repositories Backup

Describe the issue: 
The guide describes a service called pulp-server which does not exist. The pulp related services are called pulp_celerybeat, pulp_resource_manager and pulp_workers.

Suggestions for improvement: 
Documentation should state the appropriate services to stop for successfully taking a offline backup.

Additional information:
Comment 1 RHEL Program Management 2014-11-07 11:13:47 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Athene Chan 2014-11-10 22:53:42 UTC 
Hello Johan,

We'll add this into our document prioritization list for review. Possibly going in on the 6.1 release. We'll update this ticket once we start working on it.

Thank you for your feedback!

Cheers,
Athene
Comment 6 David O'Brien 2015-02-24 02:35:22 UTC 
*** Bug 1195126 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.