fedora-infrastructure

#8217 Switch from libmodulemd-2.x (epel7server-infra) to libmodulemd2 (epel) on the MBS servers
Closed: Fixed by mizdebsk. Opened by mprahl.

Closed: Fixed
Reopen Issue

This is the production version of #8215.

Now that #8206 is complete, I'd like to migrate MBS to use libmodulemd2 from EPEL. This requires a complicated yum transaction, so I need to do this on the server itself and not through an existing Ansible playbook. I have sudo access on the backend server, but I don't have sudo access on the frontend servers:
mbs-frontend01.phx2.fedoraproject.org
mbs-frontend02.phx2.fedoraproject.org

Could you please give the mbs-admins group sudo access to these servers?

For production I would prefer to run the update myself. Can you provide me with instructions what needs to be done?

@mizdebsk here are the commands I used in stage. If the module-build-service RPM is to be upgraded and not removed, then the command is correct.

yum shell
remove libmodulemd1
downgrade libmodulemd-1.6.3-1.el7.x86_64
remove python2-libmodulemd
install module-build-service-2.27.0-3.el7.infra
run
exit

Once that is run, for some reason, libmodulemd leaves a broken symlink, so the following command is required:

rm -f /lib64/libmodulemd.so.1
ln -s /lib64/libmodulemd.so.1.6.3 /lib64/libmodulemd.so.1

Could we coordinate to do this together over IRC? Thank you for your help.

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

Metadata Update from @mizdebsk:
- Issue assigned to mizdebsk
- Issue tagged with: mbs

Done.

Metadata Update from @mizdebsk:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata

mbs

None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.