You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 29, 2018. It is now read-only.
Hey all,
I've had a couple of issues over the last year with Satellite 6 which have required the use of katello-remove. When you do this however, it removes all of repositories (and perhaps other content) which pulp has synchronized (sometimes several hundred gig).
My suggestion is that an option is added to katello-remove which allows the user to preserve the pulp repositories (and RPMS) but removes everything else, so the user does not need to resync everything when they re-run the installer?
How does this suggestion sound? Obviously this will involve preserving the mongo database as well. My suggestion is to basically make this an optional option.
Cheers,
Calvin
The text was updated successfully, but these errors were encountered:
I think this makes sense @CalvinHartwell. The mongodb would need to still be wiped because all of the repositories are also being removed from Katello so the "structure" of repositories wouldn't make sense anymore. However, as you say, persisting the content on disk would speed up a rebuild.
For better visibility, I would recommend re-filling this issue here [1].
Hey all,
I've had a couple of issues over the last year with Satellite 6 which have required the use of katello-remove. When you do this however, it removes all of repositories (and perhaps other content) which pulp has synchronized (sometimes several hundred gig).
My suggestion is that an option is added to katello-remove which allows the user to preserve the pulp repositories (and RPMS) but removes everything else, so the user does not need to resync everything when they re-run the installer?
How does this suggestion sound? Obviously this will involve preserving the mongo database as well. My suggestion is to basically make this an optional option.
Cheers,
The text was updated successfully, but these errors were encountered: