Bug 965415
Summary: | Bugzilla tries to write to shadow db | ||
---|---|---|---|
Product: | [Community] Bugzilla | Reporter: | Petr Matousek <pmatouse> |
Component: | Email Notifications | Assignee: | Simon Green <sgreen> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | tools-bugs <tools-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.4 | CC: | cperry, dhoward, ebaak, iheim, jfearn, jfeeney, jingwang, jmoyer, jogreene, lyarwood, rjoost |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 4.4rc2-3.1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-05-22 07:09:23 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: |
Description
Petr Matousek
2013-05-21 08:28:39 UTC
This error has been reported many times, so I need to get to the bottom of it. Unfortunately, I'm not exactly sure of where the problem is. As a background, Red Hat have an extension that adds a remove me from the CC: list that uses a token to authenticate. The error occurs when generating this token. It appears that it is trying to put the token on the slave database, and not the master. This only started occurring in Red Hat Bugzilla 4.4, so something has changed since 4.2.5-8 and this release. Verified on qe test env version 4.4.rc2-3.1(20130522) --> pass Verify steps: 1. login as redhat account. 2. visit show bug page of bug 560484 which has 688 users in cc list. 3. change the status of this bug to 'Assigned' and click 'save changes'. then expected results: large quantity email notifications message displaying on the top, and the status has been set to 'Assigned' without errors. 4. edit the cc list to remove one account, and meantime change the status of this bug to 'CLOSED:ERRATA' and click 'save changes'. then expected results: large quantity email notifications message displaying on the top, and the status has been set to 'CLOSED:ERRATA' without errors. Actual results: same with expected results. |