Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Description of problem:
If /var/lib/mongodb is mountpoint instead of simple folder
# satellite-maintain content remove-pulp2 will fail with error below.
/ Deleting pulp2 data directories [FAIL]
Failed executing rm -rf /var/lib/mongodb/, exit status 1:
rm: cannot remove ‘/var/lib/mongodb/’: Device or resource busy
Version-Release number of selected component (if applicable):
6.10.2
How reproducible:
Always
Steps to Reproduce:
1. Have Satellite 6.9 with /var/lib/mongodb as LVM (mountpoint)
2. Migrate content to pulp3
3. Upgrade to 6.10 (Content switchover as part of it)
4. # satellite-maintain content remove-pulp2
Actual results:
/ Deleting pulp2 data directories [FAIL]
Failed executing rm -rf /var/lib/mongodb/, exit status 1:
rm: cannot remove ‘/var/lib/mongodb/’: Device or resource busy
Expected results:
Running Remove Pulp2 and mongodb packages and data
================================================================================
Remove pulp2:
WARNING: All pulp2 packages will be removed with the following commands:
# rpm -e pulp-docker-plugins pulp-ostree-plugins pulp-puppet-plugins pulp-puppet-tools pulp-rpm-plugins pulp-selinux pulp-server python-bson python-mongoenginctar python-pulp-common python-pulp-docker-common python-pulp-integrity python-pulp-oid_validation python-pulp-ostree-common python-pulp-puppet-common python-p python-pulp-rpm-common python-pulp-streamer python-pymongo python-pymongo-gridfs python2-amqp python2-billiard python2-celery python2-django python2-kombu python2-vine pulp-katello pulp-maintenance python3-pulp-2to3-migration
# yum remove rh-mongodb34-*
# yum remove squid mod_wsgi
All pulp2 data will be removed.
# rm -rf /var/lib/pulp/published
# rm -rf /var/lib/pulp/content
# rm -rf /var/lib/pulp/importers
# rm -rf /var/lib/pulp/uploads
# rm -rf /var/lib/mongodb/
# rm -rf /var/cache/pulp
Do you want to proceed?, [y(yes), q(quit)] y
\ Removing pulp2 packages
- Removing mongo packages
/ Removing additional packages
\ Dropping migration tables
/ Dropping migrations
- Done deleting pulp2 data directories
\ stopping pulpcore-content
Warning: Stopping pulpcore-api.service, but it can still be activated by:
pulpcore-api.socket
Warning: Stopping pulpcore-content.service, but it can still be activated by:
pulpcore-content.socket
- Done restarting pulpcore services [OK]
--------------------------------------------------------------------------------
Additional info:
As workaround can be /var/lib/mongodb umounted, updated fstab, remove-pulp2 and destroy LVM.