Skip to content
This repository was archived by the owner on Sep 12, 2024. It is now read-only.
This repository was archived by the owner on Sep 12, 2024. It is now read-only.

SecondaryAAA setting is problematic #1117

@haozturk

Description

@haozturk

Impact of the bug
Unified/assignor.py

Describe the bug
SecondaryAAA setting fails if there is a campaign whose secondaryAAA is False and another one True when the former comes after the latter because of this line [1]

[1] https://github.com/CMSCompOps/WmAgentScripts/blob/python3-migration-fast/Unified/assignor.py#L271

How to reproduce it
Clone this workflow and assign it w/ Unified/assignor.py in this version [1]

[1] https://github.com/CMSCompOps/WmAgentScripts/tree/245ad3402dd4883bbc1bc61e138bd8645d8bbbf9

Expected behavior
For a given workflow, if there is a campaign whose secondaryAAA is true, TrustPUSitelists of the request should be True

Additional context and error message
None

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions