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.

Sign up for GitHub

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

Jump to bottom

rucio download does not respect protocol order #1222

Closed
mlassnig opened this issue Jun 3, 2018 · 1 comment
Closed

rucio download does not respect protocol order #1222

mlassnig opened this issue Jun 3, 2018 · 1 comment
Assignees
@TWAtGH
Labels
bug Clients
Milestone
1.17.0-clients

Comments

@mlassnig
Copy link
Contributor

mlassnig commented Jun 3, 2018

Motivation

The order of selected protocols is not correct in rucio download. (Using list_replicas directly produces the correct order, however)
@TWAtGH
Copy link

TWAtGH commented Jun 4, 2018

This is not a bug but a missing feature. Rucio download does respect the order but it's not able to determine if lan or wan should be used. Instead it always uses the default (=wan).

@bari12 bari12 mentioned this issue Jun 12, 2018
Closed
@TWAtGH TWAtGH self-assigned this Jun 12, 2018
This was referenced Jun 12, 2018
Closed
Merged
@bari12 bari12 changed the title clients: rucio download does not respect protocol order rucio download does not respect protocol order Jun 15, 2018
bari12 added a commit that referenced this issue Jun 19, 2018
@bari12
Merge pull request #1254 from TWAtGH/feature-669-switch_clidownload_t…
c2c0fc8 
…o_api

Clients: switched bin/rucio download to API Fix #490 #567 #669 #1222 #1263
@bari12 bari12 added this to the 1.16.5-clients milestone Jun 19, 2018
@bari12 bari12 closed this as completed Jun 19, 2018
@bari12 bari12 modified the milestones: 1.16.5-clients, 1.17.0-clients Jun 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@TWAtGH TWAtGH

Labels
bug Clients
Projects
None yet
Milestone
1.17.0-clients
Development

No branches or pull requests
3 participants
@mlassnig @bari12 @TWAtGH