#9324 Bugzilla assignee sync script assigns some bugs to orphan by accident
Opened 2 days ago by churchyard. Modified 13 hours ago

See for example https://bugzilla.redhat.com/show_bug.cgi?id=1699483#c2 -- this seems to be a mistake because https://src.fedoraproject.org/modules/maven still says it is owned by @mizdebsk.


@zlopez you've been working on this code-base recently, do you remember seeing this?

This is not limited to modules:

https://bugzilla.redhat.com/show_bug.cgi?id=1742427#c2

https://src.fedoraproject.org/rpms/python2-django1.11

That project is retired in rawhide and the bug is a rawhide bug, so that one looks fine actually

That project is retired in rawhide and the bug is a rawhide bug

So if anything, I suggest it should be closed, not assigned to orphan. The package is not orphaned. This is confusing :/

This is not limited to modules:

https://bugzilla.redhat.com/show_bug.cgi?id=1742427#c2

https://src.fedoraproject.org/rpms/python2-django1.11

That project is retired in rawhide and the bug is a rawhide bug, so that one looks fine actually

This is how it should work, the retired packages are still updated, but not created.

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: dev, medium-gain, medium-trouble

2 days ago

When testing the new distgit_bugzilla_sync toddler. I tried to check the modules/maven project and the script is consider it retired, because there is no active branch in PDC.

Here is the project info updated by the active branch query from PDC:

{'namespace': 'modules', 'name': 'maven', 'poc': 'mizdebsk', 'epelpoc': 'mizdebsk', 'watchers': ['mizdebsk'], 'summary': None, 'branches': [['master', False], ['f27', False], ['f28', False], ['3.5', False], ['f29', False], ['3.6', False]], 'products': ['Fedora Modules'], 'products_poc': {'Fedora Modules': 'orphan'}, 'products_retired': {'Fedora Modules': True}}

It sounds like the script is doing what it should do.

@mohanboddu @humaton is it expected that the master branch of a module can be inactive?

Login to comment on this ticket.

Metadata
Boards 1
dev Status: Backlog