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 1898690 - parameter "crypt_type" should not be unique
Summary: parameter "crypt_type" should not be unique
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: resource-agents
Version: 8.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: Oyvind Albrigtsen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-17 20:27 UTC by Corey Marthaler
Modified: 2021-05-18 15:11 UTC (History)
4 users (show)

Fixed In Version: resource-agents-4.1.1-76.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 15:11:15 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)

Description Corey Marthaler 2020-11-17 20:27:20 UTC 
Description of problem:
I attempted to create a second crypt resource and got this error. I'm curious if we shouldn't just be defaulting to luks2 anyways. Are we really supporting the luks1 format in a cluster? Anyways, it certainly shouldn't be a unique attr.


From the resource-agent:
<parameter name="crypt_type" unique="1" required="1">
<longdesc lang="en">
Encryption (device) type (e.g. "luks" or "luks2").


[root@host-093 ~]# pcs resource create crypt2 --force --group HA_STSRHTS130852 ocf:heartbeat:crypt crypt_dev="luks_lv2" crypt_type=luks2 key_file=/etc/luks_key_file encrypted_dev=d58f7a61-18bb-47aa-84fe-d82998cfc930

Warning: Value 'luks2' of option 'crypt_type' is not unique across 'ocf:heartbeat:crypt' resources. Following resources are configured with the same value of the instance attribute: 'crypt1'


Version-Release number of selected component (if applicable):
Name        : resource-agents
Version     : 4.1.1
Release     : 74.el8
Architecture: x86_64
Install Date: Tue 17 Nov 2020 09:43:50 AM CST
Group       : System Environment/Base
Size        : 1506675
License     : GPLv2+ and LGPLv2+
Signature   : (none)
Source RPM  : resource-agents-4.1.1-74.el8.src.rpm
Build Date  : Wed 11 Nov 2020 03:03:44 AM CST
Comment 1 Oyvind Albrigtsen 2020-11-24 11:28:48 UTC 
https://github.com/ClusterLabs/resource-agents/pull/1584
Comment 4 Corey Marthaler 2020-12-01 23:49:21 UTC 
Fix verified in the latest rpm resource-agents-4.1.1-80.el8.x86_64.

I was able to create many gfs+crypt+lvm resource groups all using the same crypt_type now.


/tmp/luks_key_file -> host-073:/etc/luks_key_file
/tmp/luks_key_file -> host-092:/etc/luks_key_file
/tmp/luks_key_file -> host-093:/etc/luks_key_file
Creating VG STSRHTS130851 out of /dev/sdf2 /dev/sdf1 /dev/sdc2
Creating HA striped LV(s) and gfs2 filesystems on VG STSRHTS130851
        lvcreate --yes --activate sy --type striped -L 8G -i 2 -n lv STSRHTS130851
cryptsetup luksFormat /dev/STSRHTS130851/lv --type luks2 --key-file=/etc/luks_key_file
LUKS_UUID=d80704d1-b15f-4207-9df8-7eaf7ae5a2e8
cryptsetup luksOpen /dev/STSRHTS130851/lv luks_lv1 --key-file=/etc/luks_key_file
        Creating gfs2 filesystem
        mkfs.gfs2 -j 3 -J 32 -t STSRHTS13085:STSRHTS130851-lv /dev/mapper/luks_lv1 -O
cryptsetup luksClose luks_lv1


pcs resource create lv1 --group HA_STSRHTS130851 ocf:heartbeat:LVM-activate lvname="lv" vgname="STSRHTS130851" activation_mode=shared vg_access_mode=lvmlockd
pcs resource create crypt1 --force --group HA_STSRHTS130851 ocf:heartbeat:crypt crypt_dev="luks_lv1" crypt_type=luks2 key_file=/etc/luks_key_file encrypted_dev=d80704d1-b15f-4207-9df8-7eaf7ae5a2e8
pcs resource create fs1 --group HA_STSRHTS130851 Filesystem device="/dev/mapper/luks_lv1" directory="/mnt/fs1" fstype="gfs2" "options=noatime" op monitor interval=10s
pcs resource clone HA_STSRHTS130851
Creating VG STSRHTS130852 out of /dev/sdc1 /dev/sdd2 /dev/sdd1
Creating HA striped LV(s) and gfs2 filesystems on VG STSRHTS130852
        lvcreate --yes --activate sy --type striped -L 8G -i 2 -n lv STSRHTS130852
cryptsetup luksFormat /dev/STSRHTS130852/lv --type luks2 --key-file=/etc/luks_key_file
LUKS_UUID=ef277de5-8163-49c2-89dd-2d3e24e6c852
cryptsetup luksOpen /dev/STSRHTS130852/lv luks_lv2 --key-file=/etc/luks_key_file
        Creating gfs2 filesystem
        mkfs.gfs2 -j 3 -J 32 -t STSRHTS13085:STSRHTS130852-lv /dev/mapper/luks_lv2 -O
cryptsetup luksClose luks_lv2


pcs resource create lv2 --group HA_STSRHTS130852 ocf:heartbeat:LVM-activate lvname="lv" vgname="STSRHTS130852" activation_mode=shared vg_access_mode=lvmlockd
pcs resource create crypt2 --force --group HA_STSRHTS130852 ocf:heartbeat:crypt crypt_dev="luks_lv2" crypt_type=luks2 key_file=/etc/luks_key_file encrypted_dev=ef277de5-8163-49c2-89dd-2d3e24e6c852
pcs resource create fs2 --group HA_STSRHTS130852 Filesystem device="/dev/mapper/luks_lv2" directory="/mnt/fs2" fstype="gfs2" "options=noatime" op monitor interval=10s
pcs resource clone HA_STSRHTS130852
Creating VG STSRHTS130853 out of /dev/sdb2 /dev/sdb1 /dev/sde2
Creating HA striped LV(s) and gfs2 filesystems on VG STSRHTS130853
        lvcreate --yes --activate sy --type striped -L 8G -i 2 -n lv STSRHTS130853
cryptsetup luksFormat /dev/STSRHTS130853/lv --type luks2 --key-file=/etc/luks_key_file
LUKS_UUID=8cc87847-ec38-403a-81ab-4b0e79586a1b
cryptsetup luksOpen /dev/STSRHTS130853/lv luks_lv3 --key-file=/etc/luks_key_file
        Creating gfs2 filesystem
        mkfs.gfs2 -j 3 -J 32 -t STSRHTS13085:STSRHTS130853-lv /dev/mapper/luks_lv3 -O
cryptsetup luksClose luks_lv3


pcs resource create lv3 --group HA_STSRHTS130853 ocf:heartbeat:LVM-activate lvname="lv" vgname="STSRHTS130853" activation_mode=shared vg_access_mode=lvmlockd
pcs resource create crypt3 --force --group HA_STSRHTS130853 ocf:heartbeat:crypt crypt_dev="luks_lv3" crypt_type=luks2 key_file=/etc/luks_key_file encrypted_dev=8cc87847-ec38-403a-81ab-4b0e79586a1b
pcs resource create fs3 --group HA_STSRHTS130853 Filesystem device="/dev/mapper/luks_lv3" directory="/mnt/fs3" fstype="gfs2" "options=noatime" op monitor interval=10s
pcs resource clone HA_STSRHTS130853
pcs constraint order start locking-clone then HA_STSRHTS130853-clone



[root@host-073 ~]# pcs status
Cluster name: STSRHTS13085
Cluster Summary:
  * Stack: corosync
  * Current DC: host-093 (version 2.0.4-6.el8-2deceaa3ae) - partition with quorum
  * Last updated: Tue Dec  1 17:44:38 2020
  * Last change:  Tue Dec  1 15:40:53 2020 by root via cibadmin on host-073
  * 3 nodes configured
  * 36 resource instances configured

Node List:
  * Online: [ host-073 host-092 host-093 ]

Full List of Resources:
  * fence-host-073      (stonith:fence_xvm):     Started host-073
  * fence-host-092      (stonith:fence_xvm):     Started host-092
  * fence-host-093      (stonith:fence_xvm):     Started host-093
  * Clone Set: locking-clone [locking]:
    * Started: [ host-073 host-092 host-093 ]
  * Clone Set: HA_STSRHTS130851-clone [HA_STSRHTS130851]:
    * Started: [ host-073 host-092 host-093 ]
  * Clone Set: HA_STSRHTS130852-clone [HA_STSRHTS130852]:
    * Started: [ host-073 host-092 host-093 ]
  * Clone Set: HA_STSRHTS130853-clone [HA_STSRHTS130853]:
    * Started: [ host-073 host-092 host-093 ]
Comment 6 errata-xmlrpc 2021-05-18 15:11:15 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (resource-agents bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:1736
Note You need to log in before you can comment on or make changes to this bug.