Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Bug: Unmerged scanner does not use the right server config #858

Open
dynamic-entropy opened this issue Oct 18, 2024 · 2 comments
Open

Bug: Unmerged scanner does not use the right server config #858

dynamic-entropy opened this issue Oct 18, 2024 · 2 comments
Labels

Comments

@dynamic-entropy
Copy link
Contributor

Bug Description

CE (main) and Unmerged scans by consistency check seem to use different source for server configuration.

I believe both should use the same.
If that is not the case, they should be added to the gitlab conf separately as part of #820
server configuration sources

Reproduction Steps

No response

Expected Behavior

No response

Possible Solution

No response

Related Issues

Unmerged scans of KIT fail: https://cmsweb.cern.ch/rucioconmon/unmerged/show_rse?rse=T1_DE_KIT_Disk
While main scans are alright: https://cmsweb.cern.ch/rucioconmon/ce/show_rse?rse=T1_DE_KIT_Disk

FYI @eachristgr @amanrique1 @mrguilima
Perhaps you guys would like to fix this for all other sites that you modified the config for during your effort to fix problems with CE.

@mrguilima
Copy link

I have a bunch of changes to config.yaml, which fixes several sites in the CE page.
I need help on how to make those changes permanent.

@dynamic-entropy
Copy link
Contributor Author

The current way to make them permanent depends on which all sources the config is picked from.
Can they be changed in rse_attribute?
Are they mounted from flux like the main volume: https://github.com/guyzsarun/rucio-flux/blob/main/apps/production/prod-consistency-jobs.yaml
And finally, are they built into the image?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants