#11419 Cleaning old stuff from koji composes directories
Opened 2 years ago by mattia. Modified 2 months ago

Describe the issue

After asking in fedora-infra mailing list I'd like to raise attention to some old content that can be cleaned from koji's compose directories:

Adding a note from kevin:

probibly a note in the end of life sop to clean
up that. but it has to be done in the right order. ie, you should push
out and make sure the updates sync script is no longer trying to sync
the just now eoled release before removing the compose directory for it
(otherwise it may sync an empty repo to the master mirrors)

When do you need this? (YYYY/MM/DD)

No deadlines

If we cannot complete your request, what is the impact?

Nothing serious, but I suppose we can free some space in Koji and I don't know if we're wasting bandwith synchronizing old, unneeded stuff.


Metadata Update from @kevin:
- Issue tagged with: medium-gain, medium-trouble, ops

2 years ago

The composes [[ release.id_prefix.title() ]]- were created when we tested shared pungi config for Bodhi and it didn't work as expected.

Metadata Update from @jnsamyak:
- Issue tagged with: meeting

8 months ago

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

8 months ago

From the cleanups above-mentioned, only in https://kojipkgs.fedoraproject.org/compose/iot/ are still there from back - Fedora 31; which I have reached out to the folks to ensure before clearing those to confirm they are not using it!

Otherwise for other two
- in https://kojipkgs.fedoraproject.org/compose/updates/ there are
composes back to Fedora 31, EPEL6, Fedora Modular 30
This seems DONE

I'll bring this up in our releng call as well, as discussed today we should keep it for only active releases which should be 39, 40 & 41;

yeah, we typically do not do iot, and let them handle it. ;)

UPDATE: I confirmed this with IOT folks last time, and @pbrobinson is looking at archiving some of those older composes before removing them!

Metadata Update from @jnsamyak:
- Issue untagged with: meeting

6 months ago

Hey @pbrobinson

Did you get time around the iot old composes?

Metadata Update from @jnsamyak:
- Assignee reset

4 months ago

Dropping myself from this, this has been waiting for it compose for giving us the confirmation; once they do we can close this otherwise this is okay!

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

3 months ago

So, we had a email thread a while back discussing things and came to some conclusion.

@jnsamyak is going to archive those iot releases and delete the ones listed.

Log in to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog