Red Hat Bugzilla – Bug 849859
Bot should restore the needinfo flag after vendor entered the leverage IDs.
Last modified: 2015-11-30 02:40:01 EST
email@example.com entered some leverage IDs on 2012-08-14,Bot did nothing after that,since the last_update_person is non-reviewer,bot should place a comment there for attention and restore the needinfo flag on reviewer.
This is actually a catalog bug I think. Setting needinfo on weishen.
It can be easier to fix it on hwcertbot side
but that means there a gap between when the work is entered (process.cgi) and when the work is identified, when hwcertbot goes to reset some flags.
(In reply to comment #3)
> but that means there a gap between when the work is entered (process.cgi)
> and when the work is identified, when hwcertbot goes to reset some flags.
right, now all changes to hwcert data won't be recorded in bz db and the bot currently depends on bz data, so there is a gap
Catalog knows about both table sets so it should be able to set the flag when the testplan table changes resolving the gap.
bot just cares about the last update person, if catalog sets flag on each action, it doesn't make sense
Is the leverage work flag being properly set when the vendor adds the leverage id's by the catalog?
(In reply to comment #7)
> Is the leverage work flag being properly set when the vendor adds the
> leverage id's by the catalog?
Yes, it works,but bot doesn't deal with leverage certs without needinfo, which is a bug
Ah, I see. Is there any reason why needinfo is required in addition to leverage? Seems like removing that dependency would be the fix?
According to reviewers, this is fixed and moved to Done.