RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1674426 - [Docs] fix pcs command for creating lvm resource
Summary: [Docs] fix pcs command for creating lvm resource
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: Documentation
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: 8.0
Assignee: Steven J. Levine
QA Contact: RHEL DPM
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-11 10:40 UTC by Roman Bednář
Modified: 2019-05-22 04:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-20 17:01:00 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Roman Bednář 2019-02-11 10:40:13 UTC 
Document URL: 
https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_and_managing_high_availability_clusters/#proc_configuring_resources_for_nfs_server_in_a_cluster-configuring-ha-nfs

Section Number and Name: 
6.3. Configuring the resources and resource group for an NFS server in a cluster

Describe the issue: 
Step 1 tells users to create 'LVM' resource. This one no longer exists in RHEL8 and was replaced with LVM-activate.

In fact the entire pcs command seems to be obsolete since the parameters for LVM-activate are different.

Suggestions for improvement:
Use current RHEL8 command syntax. A correct example of it is actually in the same doc in section 19 step 10.i.
Comment 1 Steven J. Levine 2019-03-01 16:08:35 UTC 
Info from Oyvind Albrigtsen, in response to me:



On 27/02/19 12:55 -0600, slevine wrote:
> Oyvind (et al):
>
> For the RHEL 8 basic cluster configuration example procedure (for an
> http server on 2 nodes), we created an LVM-activate resource with the
> following command:
>
> pcs resource create my_lvm ocf:heartbeat:LVM-activate vgname=my_vg
> activation_mode=exclusive vg_access_mode=system_id --group apachegroup
>
> This was the replacement in the example for the following RHEL 7 command:
>
> pcs resource create my_lvm LVM volgrpname=my_vg exclusive=true --group
> apachegroup
>
> I have some questions:
>
> 1.
>
> What does vg_access_mode system_id do?
It makes it use the system_id access_mode that doesnt require a locking
manager, which is the new access_mode to use instead of tagging,
which is what's used by the LVM-agent if you specify exclusive=true
without setting up clvm.
>
> 2.
>
> Support engineer Reid Wahl noted the following:
>
>
> "activation_mode=exclusive" is the default value and does not need to be
> specified at all. Additionally, vg_access_mode=system_id and
> vg_access_mode=tagging force exclusive activation. So while it's fine to
> be explicit, it's unnecessary for those two reasons.
>
> Should I remove "activation_mode=exclusive" from the example, or do I
> leave it in for clarity?
Correct. No need to keep it. exclusive isnt default for the old LVM
agent, so we had to use it there.
>
> 3.
>
> In a separate procedure for configuring an NFS server in a cluster, we
> had a similar step and used this command in RHEL 7 to create an LVM
> resource:
>
> pcs resource create my_lvm LVM volgrpname=my_vg exclusive=true --group
> nfsgroup
>
> As Roman noted in BZ 1660794, that command is, of course, no longer
> correct for RHEL 8.  Would I use the same command as in the http example:
>
> pcs resource create my_lvm ocf:heartbeat:LVM-activate vgname=my_vg
> activation_mode=exclusive vg_access_mode=system_id --group nfsgroup
>
> (That's assuming we leave in the "access_mode parameter.)
Correct.
>
> Thanks,
>
> Steven
Note You need to log in before you can comment on or make changes to this bug.