Bug 956199
| Summary: | received comment notification but comment is not visible | ||
|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | Michal Skrivanek <michal.skrivanek> |
| Component: | Email Notifications | Assignee: | Simon Green <sgreen> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Matt Tyson 🤬 <mtyson> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2 | CC: | bcao, ebaak, ecohen, jingwang, jmcdonal, jpokorny, jskeoch, ksrot, rjoost, sgreen, thenzl, ykatabam |
| Target Milestone: | 4.4 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 4.4.4019 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-05-07 00:58:02 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1083454 | ||
| Bug Blocks: | 1017534, 1087687 | ||
|
Description
Michal Skrivanek
2013-04-24 12:47:45 UTC
(In reply to comment #0) > Description of problem: > I got an email notification about new comment but the comment is not in > bugzilla web interface I am seeing this to ykatabam: Any idea what happened here? I see you changed the needinfo and made a comment 32 minutes after this message is meant to have happened -- simon I believe there was a conflict that both of us attempted to save messages at the same time. When I saw the screen notifying the conflict, I went back to the previous screen and then completed my message (added a few more lines) then saved again, which is comment 4. Does this explain the problem? Next time I will chose one of the options provided, instead of going back. *** Bug 963581 has been marked as a duplicate of this bug. *** (In reply to comment #2) > Does this explain the problem? No. > Next time I will chose one of the options provided, instead of going back. Going back should be safe too. - Both of these relate to flag change e-mails that are sent out, not the actual bug change e-mails. Which makes me think these e-mail is being sent out before the changes are committed. It's not going to be fixed in time for Monday's release, but I will try and get it into a hotfix. -- simon I hit this issue as well There is an upstream bug (see external trackers) that I am following that will fix this issue when the blocker is fixed. It should be backported to 4.4, but if not, we will do it ourselves. -- simon *** Bug 1003974 has been marked as a duplicate of this bug. *** FYI - I hit a similar issue a couple of days ago with Bug 1003634 - got an e-mail from bugzilla notifying on a needinfo request + a comment that is not documented anywhere within the BZ / BZ history. Additional instance of bug https://engineering.redhat.com/rt/Ticket/Display.html?id=268059 for data points. This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug. -- simon |