Bug 2212228 - Membership review job throws global kill switch
Summary: Membership review job throws global kill switch
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Extensions
Version: 5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-04 22:08 UTC by Jeff Fearn 🐞
Modified: 2023-07-03 00:17 UTC (History)
0 users

Fixed In Version: 5.0.4-rh88
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-03 00:17:37 UTC
Embargoed:


Attachments (Terms of Use)

Description Jeff Fearn 🐞 2023-06-04 22:08:27 UTC
Description of problem:
If there is a mismatch between the flag name on a membership review bug and the group it is for, then the global kill switch is thrown.

Version-Release number of selected component (if applicable):
5.0.4-rh86

How reproducible:
Always

Steps to Reproduce:
1. Create a group
2. Add the group to the membership workflow
3. Create an approval flag
4. Add someone to the group
5. Create a membership review for the membership
6. Change the group name
7. Trigger the "Close Old Group membership requests" BRE rule

Actual results:
The global kill switch is thrown.

Expected results:
The kill switch is limited to the BRE group the rule belongs to.

Additional info:

Comment 2 Jeff Fearn 🐞 2023-06-28 03:38:19 UTC
On QA server.

1. Create a new group in the Red Hat category
2. Configure the group to require group signoff
3. Add a user to the group
4. Change the group name
5. Wait for the clean up job to run.

The kill switch is thrown and is limited to the Workflow BRE group.

Comment 3 Jeff Fearn 🐞 2023-06-28 23:01:36 UTC
This fix has been deployed to stage Bugzilla for a short public testing phase.

https://bugzilla.stage.redhat.com

Comment 4 Jeff Fearn 🐞 2023-07-03 00:17:37 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.