Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1660135

Summary:	[DDF] I had to also install the dlm package in order for step 2 to create a working resource.
Product:	Red Hat Enterprise Linux 8	Reporter:	Direct Docs Feedback <ddf-bot>
Component:	Documentation	Assignee:	Steven J. Levine <slevine>
Documentation sub component:	DDF	QA Contact:
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	unspecified
Priority:	high	CC:	nwahl, rhel-docs, slevine
Version:	8.0	Flags:	tcapek: mirror+
Target Milestone:	rc
Target Release:	8.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-17 19:03:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Direct Docs Feedback 2018-12-17 15:19:29 UTC

I had to also install the dlm package in order for step 2 to create a working resource.

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8-beta/html/configuring_and_managing_high_availability_clusters/assembly_configuring-gfs2-in-a-cluster-configuring-and-managing-high-availability-clusters#annotations:6c0ab126-d91a-4fb4-9f91-608970b68d36

Comment 1 Reid Wahl 2018-12-28 04:54:11 UTC

Verified. As it stands, the dlm package can't be a dependency of the lvm2-lockd package AFAIK. lvm2-lockd and dlm-lib are in AppStream, while dlm is in Resilient Storage.

Can we check with PM on whether this is the desired placement?

Comment 2 Steven J. Levine 2019-03-01 15:27:54 UTC

I had this exchange with Chris Feist:

----
>
> In our procedure for configuring a GFS2 file system in a cluster, we
> said this:
>
> "On both nodes of the cluster, install the lvm2-lockd and gfs2-utils
> packages. The lvm2-lockd package is part of the AppStream channel and
> the gfs2-utils package is part of the Resilient Storage channel.
>
> # yum install lvm2-lockd gfs2-utils"
>

Lets add dlm to that yum install line so it now reads:
# yum install lvm2-lockd gfs2-utils dlm

I'm verifying that with Dave, but I think we can go with that for now.
----

So for now it appears to be the desired placement and I'm adding it to the procedure.

Comment 3 Steven J. Levine 2019-03-01 15:37:49 UTC

I asked Chris Feist if that package placement is desired.  I'll update the docs if that changes, but for now I specify which channel each of the three packages is in.