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

Set up of Siesta code is wrong. #42

Closed
bosonie opened this issue Jul 8, 2020 · 6 comments · Fixed by marvel-nccr/ansible-role-siesta#8
Closed

Set up of Siesta code is wrong. #42

bosonie opened this issue Jul 8, 2020 · 6 comments · Fixed by marvel-nccr/ansible-role-siesta#8

Comments

@bosonie
Copy link
Contributor

bosonie commented Jul 8, 2020

Not even sure if the issue is here, but the code siesta-v4.1-rc1-siesta available from the aiida set up in the quantum mobile (last version at least) contains a wrong remote absolute path. It shows local/Obj instead of local/bin.
This makes aiida_siesta unusable in the quantum mobile.

@ltalirz
Copy link
Member

ltalirz commented Jul 8, 2020

ok, thanks for reporting!
would you mind making a PR to fix the role?

Edit: Indeed, the validation of file paths for codes is a contentious issue aiidateam/aiida-core#868 but here it would have helped

@bosonie
Copy link
Contributor Author

bosonie commented Jul 8, 2020

Sorry @ltalirz but I have no idea about the mechanism.
Is it here?
https://github.com/marvel-nccr/ansible-role-siesta/blob/ab36d895eba05504d0ede8589ff9fbb6ca862148/defaults/main.yml#L26

When you install siesta, the executable is in the Obj folder of the siesta package. However in the quantum mobile all the executables seem to be in /usr/local/bin. I guess you copy them automatically after installation.

@ltalirz
Copy link
Member

ltalirz commented Jul 8, 2020

Indeed - I see the executables are now copied one by one https://github.com/marvel-nccr/ansible-role-siesta/blob/ab36d895eba05504d0ede8589ff9fbb6ca862148/tasks/main.yml#L81-L132 (I guess this was introduced by Alberto).

Simply removing the /Obj postfix should resolve the issue.

@bosonie
Copy link
Contributor Author

bosonie commented Jul 8, 2020

...mmm... I'm not understanding. The siesta executable is in the folder /usr/local/bin, so I think everything is correct from the siesta role. The problem comes in the setting up of the code in aiida. Is it done here:

- name: set up siesta codes for localhost
include_tasks: code-setup.yml
vars:
- aiida_code:
label: "siesta-{{ siesta_version }}-{{ item.name }}"
template: code.yml
executable: "{{ item.name }}"
folder: "{{ item.folder }}"
plugin: "{{ item.plugin }}"
description: "siesta v{{ siesta_version }}"
with_items: "{{ siesta_executables }}"
when:
- siesta_executables is defined
- item.plugin is defined

The item.name is correct. What is the item.folder? I'm very confused

@ltalirz
Copy link
Member

ltalirz commented Jul 8, 2020

@bosonie
Copy link
Contributor Author

bosonie commented Jul 8, 2020

Ok, now I understood. So this folder is not used in the task of the siesta-role, but it is used by the aiida-role. Ok. I'll fix it.
Cheers!

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

Successfully merging a pull request may close this issue.

2 participants