For some releases, no bugs/issues are created in Bugzilla. Missing releases are for example: solaar and thunderbird.
@zlopez can you take a look?
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: release-monitoring
@kevin This is caused by another golang package rename :-(
This time golang-github-makenowjust-heredoc is in Bugzilla golang-github-MakeNowJust-heredoc.
golang-github-makenowjust-heredoc
golang-github-MakeNowJust-heredoc
Sigh. Is there some way we could detect these and alert on them? Or catch the error and go on?
I have fixed this one.
:open_file_folder:
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
I have fix for this, that will return the message with NACK and continue working, but I can't reproduce this in staging.
There isn't any renamed repository in staging and I don't know what exactly you need to do to rename it.
I thought about this and the other way to reproduce this issue is to change the name of the component in partner-bugzilla.
More specifically golang-github-MakeNowJust-heredoc to golang-github-makenowjust-heredoc, I should be able to trigger the issue manually after this change.
It actually already seems that way. :)
Let me know if you need anything more here...
Metadata Update from @kevin: - Issue status updated to: Open (was: Closed)
I still see golang-github-MakeNowJust-heredoc in https://partner-bugzilla.redhat.com/query.cgi?format=advanced
I thought we wanted that so you could test it against the failing case? Or did you want me to fix it?
Maybe we misunderstood each other.
I need to have different name of the repository and bugzilla to test this, right now they are same on staging.
And it looks easier to rename component in partner-bugzilla than renaming the whole repository in src.stg.fp.o
There is still no Bugzilla bug for the availability of the latest solaar release.
@janvlug The reason is that this version is already packaged in Fedora.
Comparing upstream 1.0.1 against repo 1.0.1-1.fc32
In this case bugzilla issue wouldn't be created.
Maybe we misunderstood each other. I need to have different name of the repository and bugzilla to test this, right now they are same on staging. And it looks easier to rename component in partner-bugzilla than renaming the whole repository in src.stg.fp.o
So in staging I see:
You want me to make a new golang-github-makenowjust-heredoc component ? Or you want me to rename the existing one to that? Or is this a different component.
just let me know what exact component changes you need and I can do them.
@kevin I need you to rename the existing component in partner-bugzilla to golang-github-makenowjust-heredoc. I need to hit issue when the component doesn't exist in bugzilla, but the package itself exists.
Done.
Can we close this out now?
@kevin Yes, I was able to reproduce the issue and test if fix is working, which is everything I wanted to do. :-)