# satellite-maintain upgrade run --target-version 6.11
- Removing pulp2 packages                                                       
\ Removing mongo packages                                                       
\ Removing additional packages                                                 
/ Dropping migration tables                                                     
- Dropping migrations                                                           
| 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
--------------------------------------------------------------------------------
Scenario [Procedures before migrating to Satellite 6.11] failed.


A viable workaround should be:
1. install f-maintain from 6.10 (0.8.31)
2. explicitly remove pulp2 content: satellite-maintain content remove-pulp2
3. re-run the actuall 6.11 upgrade


+++ This bug was initially created as a clone of Bug #2027567 +++

Description of problem:

After upgrading to 6.10, the remove pulp2 content step fails if one of the directories being removed are dedicated mount points.


Version-Release number of selected component (if applicable):
Satellite 6.10


How reproducible:
Everytime

Steps to Reproduce:
1. Create a 6.9 Satellite with /var/lib/mongodb as a dedicated mount point.
2. Upgrade to 6.10
3. Try removing the pulp2 content:
~~~
# satellite-maintain content remove-pulp2
~~~

Actual results:
The below output is seen:
~~~
Failed executing rm -rf /var/lib/mongodb/, exit status 1:
 rm: cannot remove ‘/var/lib/mongodb/’: Device or resource busy
--------------------------------------------------------------------------------
Scenario [Remove Pulp2 and mongodb packages and data] failed.

The following steps ended up in failing state:

  [pulp-remove]

Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="pulp-remove"
~~~


Expected results:
Pulp2 content should be removed graciously, check if any of the directories being deleted are dedicated mounts or not. If they are, then delete the contents inside them but not delete the directory itself as that will still be an active mount.