Skip to content
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

Wrong cms RSE name pattern used when attaching dids #1901

Closed
sartiran opened this issue Dec 11, 2018 · 8 comments
Closed

Wrong cms RSE name pattern used when attaching dids #1901

sartiran opened this issue Dec 11, 2018 · 8 comments

Comments

@sartiran
Copy link
Contributor

Motivation

in lib/rucio/common/schema/cms.py the RSE Name pattern is

^T[0-3]_[A-Z]{2}((_[A-Za-z0-9]+)+)$

while the pattern for the rse property of ATTACHMENT is

^([A-Z0-9]+([_-][A-Z0-9]+)*)$

as a result when we add replicas to a CMS RSE whose name is not all in capitals (e.g. T1_UK_RAL_Buffer):

  • if we use add_replicas and the attach_dids it works fine
  • if we use attach_dids directly it fails with InvalidObject

Modification

Just put the same regexp for the two patterns (PR coming)

@sartiran
Copy link
Contributor Author

Created PR #1902
Maybe we may want to test it on the CERN server before merging.

@bari12
Copy link
Member

bari12 commented Dec 11, 2018

Hi Andrea,
You created this PR against the next branch (Thus it is treated as a feature). This will then only go in the Rucio 1.19.0 release in February 2019. Is this fine? Otherwise please re-create as a patch.
See https://github.com/rucio/rucio/blob/master/CONTRIBUTING.rst

@sartiran
Copy link
Contributor Author

Hi Martin,
ok sorry. I'm recreating the PR.

@sartiran
Copy link
Contributor Author

Created #1904

@bari12
Copy link
Member

bari12 commented Dec 11, 2018

That's against the hotfix branch 😄
I'll create the two PRs for master and next.

@bari12
Copy link
Member

bari12 commented Dec 11, 2018

Although I just saw you based your development off the hotfix branch (instead of master). It's not super clean to merge it like that. It would probably work fine, but we should stick to the normal workflow here.

@sartiran
Copy link
Contributor Author

I'm really sorry.. I've read the doc too quickly and understood patches go in hotfix (I do not know how, since is clearly stated). I'll recreate 2 PR one for next and one for master (both from a branch based on master, if I understand correctly)

@bari12
Copy link
Member

bari12 commented Dec 11, 2018

Hi Andrea, no worries. The workflow we have is sadly not very simple for somebody new, since it is somewhat different than most projects do it, so I can understand the confusion. Just ping me on Slack if you have any question about the setup. 😄

sartiran added a commit to sartiran/rucio that referenced this issue Dec 11, 2018
bari12 added a commit that referenced this issue Jan 9, 2019
…ern_for_attachment

bug: Fix CMS RSE Name pattern for ATTACHMENTS Fix #1901
bari12 added a commit that referenced this issue Jan 9, 2019
…ern_for_attachment

bug: Fix CMS RSE Name pattern for ATTACHMENTS Fix #1901
@bari12 bari12 added this to the 1.18.9 milestone Jan 9, 2019
TomasJavurek pushed a commit to TomasJavurek/rucio that referenced this issue Jan 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants