RHEL error after updating Prisma to 2.15.0

Bug description

After updating Prisma from 2.14.0 to 2.15.0, I started getting TypeScript errors about .prisma/client not exporting types (but only on CI), so I thought I’d manually run npx prisma generate but it throws an error:

yarn workspace foo prisma generate
yarn workspace v1.22.4
yarn run v1.22.4
$ /usr/src/app/jenkins/workspace/foo/node_modules/.bin/prisma generate
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Error: Get config /usr/src/app/jenkins/workspace/foo/node_modules/@prisma/cli/query-engine-rhel-openssl-1.0.x: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by /usr/src/app/jenkins/workspace/foo/node_modules/@prisma/cli/query-engine-rhel-openssl-1.0.x)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed.
Exit code: 1
Command: /usr/src/app/jenkins/nodejs/12.18.4/linux_x64/bin/node
Arguments: /usr/src/app/jenkins/workspace/foo/bin/yarn-1.22.4.js prisma generate
Directory: /usr/src/app/jenkins/workspace/foo/services/foo
Output:

info Visit https://yarnpkg.com/en/docs/cli/workspace for documentation about this command.

Locally I use Ubuntu and there’s no error thrown. In the changelog I saw something about RHEL, so could be related?

We’ve upgraded our RHEL base image from CentOS 6 to Amazon Linux 2. CentOS 6 reached end-of-life on November 30th, 2020. This may affect machines still running Amazon Linux 1. If you run into problems with this upgrade, please don’t hesitate to reach out.

How to reproduce

1. Update Prisma from 2.14.0 to 2.15.0
2. Run npx prisma generate
3. See above error

Expected behavior

No error.

Prisma information

Environment & setup

• OS: Red Hat Enterprise Linux Server release 7.9 (Maipo) (cat /etc/redhat-release)
• Database: MariaDB
• Node.js version: 12.18.4
• Prisma version: 2.15.0. Running prisma -v also throws the above error.

[nicksrandall]

I also have this issue and we are running RHEL7 which only supports glibc 2.17. It would be great if we could continue to support that version of glibc. Thanks for all you do!

[pantharshit00]

Thanks for reporting, we did have some build pipeline changes as CentOS 6 went EOL. We will further investigate this now.