-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
conveyor-receiver looking into wrong field name of fts message? #441
Comments
Looking into fts3 source, it seems inconsistent there: SendTransferStartMessage and SendTransferFinishMessage use "vo" but SendTransferStatusChange uses So maybe I am just looking at the wrong messages? |
Ok, using the other topic:
results in this payload, which does have the "vo" field:
|
I guess this could be closed or converted into a documentation issue. |
Description
Code in receiver.py:
https://github.com/rucio/rucio/blob/3d5cbf5d8c0e37f793bbd6f01d1064e44cfe0b4f/lib/rucio/daemons/conveyor/receiver.py#L80-L82
But dumping the activemq message, the field seems to be called "vo_name", not "vo":
Steps to reproduce
Current rucio/fts image in kubernetes
Rucio Version
35.4.1, but code in master is the same
Additional Information
No response
The text was updated successfully, but these errors were encountered: