Red Hat Bugzilla – Bug 1250282
save changes will return "Invalid Certification ID" if the corresponding bug has "Depends on" or "Blocks" which is not cert
Last modified: 2015-09-21 02:03:44 EDT
https://hardware.redhat.com/show.cgi?id=1221125 this is a hardware spec,its corresponding bug is https://bugzilla.redhat.com/show_bug.cgi?id=1221125 ,it's the block of https://bugzilla.redhat.com/show_bug.cgi?id=1105196 which is used by HP to track HP cert,so actually the #1105196 is not a cert ID but a bug ID.
When saving changes of https://hardware.redhat.com/show.cgi?id=1221125 it will return errors:
Invalid Certification ID
The cert with bug id#1105196 does not exist.
Please press Back and try again.
Seems CWE will check the "depends on" or "blocks" and the IDs must be cert IDs,otherwise it will return error.
Sometimes,vendor may use "depends on" or "blocks" to track issues or certs,we should allow this value to be bug ID as well.
Please help to fix this bug as soon as possible.
I removed the 1105196 from the blocks of 1221125 because reporter will save changes for this cert.
Do we need to allow vendors to set 'dependson' to a bug (not a cert)? If we need, I would like to take this issue to do some modification. If we don't need, just ask the reviewers to delete them will be OK. What is your opinion? Thanks a lot for your kindly help!
(In reply to Hong Tao from comment #2)
> Hi, Rob,
> Do we need to allow vendors to set 'dependson' to a bug (not a cert)? If we
> need, I would like to take this issue to do some modification. If we don't
> need, just ask the reviewers to delete them will be OK. What is your
> opinion? Thanks a lot for your kindly help!
> Best Regards,
> Hong Tao
It should not break things to have set a depends on that is not a cert. We don't have support and suggest vendors should not use bz directly, however outside of that it's reasonable that a partner might set a depends on a RHEL bug to show that it is blocking a certification so it seems correct to fix this.
The "advanced" tab has an 'other' relationship type as well which is where this kind of linking should appear in the UI although it is not controllable from there.