Description of problem: If a FAF report has associated RHEL-7.0 and RHEL-7.1 bugs and you send a duplicate report from RHEL-7.2, you will get those two bugzilla bugs. However, if you send a duplicate from RHEL-6.8, you will get empty list. If you then create a bugzilla bug for the RHEL-6.8 crash and associate the bug with the faf URL and send a duplicate report from RHEL-7.2, you will get all the associated bugs (event the RHEL-6.8 one). Version-Release number of selected component (if applicable): abrt-cli-2.1.11-35.el7.x86_64
* Maybe faf should have the bugs added to the statistics table where OS version and count is. This will link bugzillas to the respective versions, and available to view when we open the faf report. * When the email is sent it can contain the status of the bugs along with the versions they were filed for Example: I reproduced http://faf-report.itos.redhat.com/reports/467/ on RHEL 7.0, reported the crash and the reported_to file contained: # cat reported_to uReport: BTHASH=64970911b241ca64bc8eec6c89ea369ef2d8cc15 ABRT Server: URL=https://faf-report.itos.redhat.com/reports/bthash/64970911b241ca64bc8eec6c89ea369ef2d8cc15 ABRT Server: URL=https://faf-report.itos.redhat.com/reports/467/ If possible I would like this file to contain Bugzilla: RHEL 7.2 URL=https://bugzilla.redhat.com/show_bug.cgi?id=1305740 status new RHEL 7.0 URL= ? (associate an existing bug or create a bug for this version)
I tried to solve this problem many times but I never got a solution so please give me the solution. If anyone facing an issue email and have any query related to is then you can take help from this site https://www.emailcustomercareservice.com/blog/tag/oops-a-server-error-occurred-and-your-email-was-not-sent-007/
We will very likely have no resources to fix this bug during Red Hat Enterprise Linux 7 time life. Moving to upstream. If you insisted on fixing in Red Hat Enterprise Linux 7 please open a support ticket.
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
> > If possible I would like this file to contain > > Bugzilla: > RHEL 7.2 URL=https://bugzilla.redhat.com/show_bug.cgi?id=1305740 status new > RHEL 7.0 URL= ? (associate an existing bug or create a bug for this version) I think my original request does not add much value. We should not add bugs for every release for the same crash. If it makes sense, maybe just link the bug that exists for the crash with OS version it was logged in. The component team can decide if they want to fix it and back port it.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.