There is no need to explicitly add luksmeta to compose config. It will be pulled to composes automatically as a dependency of clevis.

I can see luksmeta in the latest compose, this has likely been resolved:

Searching in /mnt/redhat/nightly/latest-RHEL-7/
Client-optional/x86_64/os/Packages/luksmeta-3-1.el7.x86_64.rpm
ComputeNode-optional/x86_64/os/Packages/luksmeta-3-1.el7.x86_64.rpm
Server-optional/aarch64/os/Packages/luksmeta-3-1.el7.aarch64.rpm
Server-optional/ppc64/os/Packages/luksmeta-3-1.el7.ppc64.rpm
Server-optional/ppc64le/os/Packages/luksmeta-3-1.el7.ppc64le.rpm
Server-optional/s390x/os/Packages/luksmeta-3-1.el7.s390x.rpm
Server-optional/x86_64/os/Packages/luksmeta-3-1.el7.x86_64.rpm
Workstation-optional/x86_64/os/Packages/luksmeta-3-1.el7.x86_64.rpm

*** Bug 1449937 has been marked as a duplicate of this bug. ***

I did enforce same location by placing it to same comps group. https://code.engineering.redhat.com/gerrit/gitweb?p=comps.git;a=commit;h=87fc2b8ed6a4c020d96eee403e73293284ae1676


Lubos

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, 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-2017:1850