-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Build
-
ALL
I am unable to install mongodb community and enterprise in the 6.0 repos as of this morning. I think it's possible that a package we depend on stopped also depending on shadow-utils. Here is a docker image definition that reproduces the error:
FROM amazonlinux:2023
RUN echo $'\n\
[mongodb]\n\
name=MongoDB Repository\n\
baseurl=https://repo.mongodb.org/yum/amazon/2023/mongodb-org/6.0/x86_64/\n\
gpgcheck=1\n\
enabled=1\n\
gpgkey=https://pgp.mongodb.com/server-6.0.asc' > /etc/yum.repos.d/mongodb.repo
RUN yum install -y mongodb-org
Error logs:
Running transaction
Preparing : 1/1
Installing : openssl-1:3.0.8-1.amzn2023.0.3.x86_64 1/9
Installing : mongodb-org-database-tools-extra-6.0.15-1.amzn2023.x 2/9
Running scriptlet: mongodb-org-server-6.0.15-1.amzn2023.x86_64 3/9
/var/tmp/rpm-tmp.p37WmJ: line 2: /usr/sbin/groupadd: No such file or directory
error: %prein(mongodb-org-server-6.0.15-1.amzn2023.x86_64) scriptlet failed, exit status 127
Error in PREIN scriptlet in rpm package mongodb-org-server
Installing : mongodb-org-mongos-6.0.15-1.amzn2023.x86_64 4/9
error: mongodb-org-server-6.0.15-1.amzn2023.x86_64: install failed
Installing : mongodb-org-database-6.0.15-1.amzn2023.x86_64
This has come up before – I wonder if we should do an audit to ensure we're installing shadow-utils on every server version?