I was reviewing the ticket #1797524 and I could not either assign that ticket to myself or set a positive fedora-review flag.
Although I am still reviewing it (that's my first), I don't see the option there. Asking help in #fedora-devel, It was suggested that I'd filed this ticket.
It seems that it could be something to do with the sync of my account on FAS and BZ.
Thank you.
It may be that the script that is supposed to set your packager permissions isn't working right.
It's the 'export-bugzilla' script on fas01.
@pingou have any ideas here?
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review)
The current script uses some kind of queue mechanism implemented directly in FAS' DB.
I've been progressing on having a way to export group membership from bugzilla, so we can do: give me all the packagers in FAS and all the packagers in bugzilla and look at which are not in both, but this isn't ready yet (I hope it'll be for the new AAA).
I do not know where the current script runs, I guess in one of the FAS server? Does it send out its cron output?
It runs on fas01 and no output from the cron, but it doesn't seem to be working. ;(
Thanks for looking into this, guys.
In the meantime, do you think you could help me? Is there anything we could do? There is someone waiting for a fedora-review flag +, to have his repository created[1] :(
Thanks again!
1 https://bugzilla.redhat.com/show_bug.cgi?id=1797524
Hi Stephen, thanks for setting the +.
However, the guy could not proceed with the repository request. According to him, it was refused because < They rejected the repo because you are not the assigned reviewer :/ >.
Maybe that is the issue after all?
I meant Stephen Gallagher, who approved but is not assigned.
I've manually fixed your bugzilla account. Unset and then reset the fedora_review flag and it should all work.
We of course need to fix the sync script still.
Good news, the latest version of bugzilla that was just deployed is shipping the two fixes we needed to move the sync script off of FAS and into something that is more self-standing
Another case of this: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/YA7LGXZDRS62QQSOK6JUQVUFAL4RMQBG/
(note: I already manually fixed their account)
I believe I'm also affected by this. I cannot assign the review bug to myself or set fedora-review+, and I don't see any permission bits in bugzilla preferences.
@kevin, could you please apply the same manual fix for my account?
Done, and sorry for the hassle.
Thanks a lot! Everything works now.
Hi! I am unable to assign a review request to myself as well! It was my first case of reviewing someone else's package, and I was worried that I might be doing something wrong until I remembered the e-mail cited above...
The review in question: #1821120
@kevin, could you please do the same thing for my account?
So I've been working on https://pagure.io/Fedora-Infra/packager-sync-bz to tackle this ticket. I've been using @lyessaadi 's account as test to see if it works correctly and the annoying thing is that it seems it does not behave correctly.
If I run the script twice for @lyessaadi it tries to adjust the account both times...
I need to switch to something else, but considering I've been re-using the code from "export-bugzilla" that is in ansible, if someone wanted to double check this, it would be most appreciated. Could it be that the current script doesn't work because its code doesn't work and isn't raising an error?
I've reported the issue against bugzilla on bugzilla, let's see if they can help me/us sort this out.
@pingou can I fix @lyessaadi 's account now? Or should I hold off for a bit ?
If @lyessaadi is fine with it, I would not mind if we could hold off for a bit as this gives us a good "test-case" to make sure the new solution works.
@lyessaadi let us know if you mind waiting a little longer and we'll just fix your account :)
I am fine with it :) !
Metadata Update from @pingou: - Issue assigned to pingou
@lyessaadi Thanks :)
I think we may want to adjust your account manually now, they have confirmed that this is a bug in bugzilla itself and while they have marked it as "High priority" it will still take a little time before it is fixed and deployed.
@kevin what do you think? ^
Hello!
So, I already have Bugzilla permissions since 2/3 days now? I thought you just added them temporarily until you began testing things, am I wrong?
It was the bugzilla admins testing that re-added your permissions. ;)
I guess we can close this now as there's not anything for us to do but wait for the fix to land in bugzilla...
Metadata Update from @kevin: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)
@kevin, can you apply the manual fix to my account too? I'm unable to close an FTBFS bug on a package I adopted because the bug hasn't been reassigned to me.
Done.
@pingou didn't they deploy the fix?
@kevin, no I was hoping the old script would start working again once the issue got fixed in bugzilla (though, did we update the old script to use the new credentials?)
I'll look into this next week.
So I've had a quick look (using the new script, which allowed me to find a couple of small bugs). There are currently 30 accounts that should be sync to bugzilla, but only 11 can be done as the other 19 don't have a bugzilla account.
I'll run the script and get the 11 done.
I still would like to debug the current script though, I need to find it again
I've just found and re-run the old export-bugzilla script on fas01, it ran nicely, didn't crash, and considering the output of the new script, didn't do a thing...
Login to comment on this ticket.