Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1513103 - Clarify documentation for RHEL 6 -> RHEL 7 changes
Summary: Clarify documentation for RHEL 6 -> RHEL 7 changes
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: Documentation
Version: 7.4
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: RHEL DPM
QA Contact:
jwirch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-14 18:32 UTC by Steven J. Levine
Modified: 2019-03-06 01:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Steven J. Levine 2017-11-14 18:32:13 UTC
From a customer survey

"Working with a system based on both RHEL 6.x and RHEL 7.x server clusters, sometimes hard to navigate in the documentation what and how a specific subject changed, for example hostname configuration."

Sam Knuth has asked the customer for more details.

On first glance it's not clear whether this is a cluster issue specifically or a general RHEL issue: "hostname configuration" is not a cluster issue, but perhaps this means "configuring cluster members"?.  Also it's not clear whether this is a rhel6-rhel7 issue, or an rgmanager-Pacemaker issue.  Configuring a hostname in a RHEL 6 Pacemaker cluster should be indentical to configuring a hostname in a RHEL 7 Pacemaker cluster, for example, and the rgmanager-Pacemaker differences are far more extensive than this (and are currently summarized in the documentation).

So for now I'm opening this BZ, but it may need to be re-assigned on further information.


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