#7148 Clean up epel components in bugzilla for packages with no epel branches.
Closed 6 years ago Opened 6 years ago by ralph.

We found a bug in the bugzilla sync script today:

https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=61210be170acb90745ae3d7876d781e582376f6a

The effect of the bug is that we were creating components in bugzilla for epel for all packages - including those that didn't have any epel branches.

We should script something up to go through and find all such packages, and delete or disable those components in bugzilla.


Metadata Update from @ralph:
- Issue assigned to ralph

6 years ago

Note - I don't see a way in the python-bugzilla API to remove a component.

Hopefully this query will get out the list of all the EPEL components:

>>> details = bz.getcomponentsdetails('Fedora EPEL')

Nevermind..

HTTPError: 502 Server Error

Seems we can get info out this way:

    >>> package = bz._proxy.Component.get(dict(names=[dict(product='Fedora EPEL', component='python-requests')]))

Which gives.

>>> pprint.pprint(package)
{'components': [{'default_assignee': 'aurelien@bompard.org',
         'default_cc': ['aurelien@bompard.org',
                'cstratak@redhat.com',
                'infra-sig@lists.fedoraproject.org',
                'jeremy@jcline.org'],
         'default_docs_contact': '',
         'default_qa_contact': 'extras-qa@fedoraproject.org',
         'description': 'HTTP library, written in Python, for human beings',
         'flags': [16, 415, 1065, 312, 155],
         'id': 110166,
         'name': 'python-requests',
         'product_id': 90,
         'product_name': 'Fedora EPEL',
         'template_to_use': 'Default'}]}

In #fedora-releng, @kevin said he thinks it should be possible to remove the components in that list via XMLRPC. I'll dig into the API and see if I can find a way.

FYI - I found a way to do it. I've scripted it up and am letting it run. Will report the results back here.

Should be good to go, assuming the script running on pkgs02 doesn't go ahead and re-create them all (it was fixed, so it shouldn't, but we should check to make sure).

Metadata Update from @ralph:
- Issue status updated to: Closed (was: Open)

6 years ago

Login to comment on this ticket.

Metadata