We recently (3 months ago?) updated from one version of Katello to the next
(Foreman 1.12 to 1.13; Katello 3.1 to 3.2). During that process I also
changed the structure of our Content Views and Composite Content Views to
better reflect our structures.
Last week we started to run out of room on the server in question and I
started to look around for what was using the space.
I noticed that there was a directory that contained a lot of data about CVs
that no longer existed.
/var/lib/pulp/published/yum/master has a lot of old data in it, and
/var/lib/pulp/published/yum/master/yum_distributor seems to have all the
newer data in it.
Since the CVs in question have been "deleted" from Katello, there is no
obvious way to clean this data up.
Is this a known change and can I delete the old data from this directory
(except from yum_distributor) or is there associated meta data stuck
somewhere that requires I use another method?
cheers
L.
···
------
The most dangerous phrase in the language is, "We've always done it this
way."
Isnt there the katello-remove-orhpans script which is also called from cron?
LZ
···
On Fri, Apr 28, 2017 at 5:22 AM, Lachlan Musicman wrote:
> Hi,
>
> We recently (3 months ago?) updated from one version of Katello to the next
> (Foreman 1.12 to 1.13; Katello 3.1 to 3.2). During that process I also
> changed the structure of our Content Views and Composite Content Views to
> better reflect our structures.
>
> Last week we started to run out of room on the server in question and I
> started to look around for what was using the space.
>
> I noticed that there was a directory that contained a lot of data about CVs
> that no longer existed.
>
> /var/lib/pulp/published/yum/master has a lot of old data in it, and
>
> /var/lib/pulp/published/yum/master/yum_distributor seems to have all the
> newer data in it.
>
>
> Since the CVs in question have been "deleted" from Katello, there is no
> obvious way to clean this data up.
>
> Is this a known change and can I delete the old data from this directory
> (except from yum_distributor) or is there associated meta data stuck
> somewhere that requires I use another method?
>
> cheers
> L.
>
>
>
>
> ------
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
