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

Environment variable EGI_SITE not used #150

Closed
thebe14 opened this issue Jun 17, 2022 · 5 comments
Closed

Environment variable EGI_SITE not used #150

thebe14 opened this issue Jun 17, 2022 · 5 comments
Labels
bug Something isn't working

Comments

@thebe14
Copy link
Collaborator

thebe14 commented Jun 17, 2022

The environment variable EGI_SITE is set to a site name, but fedcloud does not use it, instead it insists to provide parameter --site or --all-sites.

Environment

  • Operating System: Ubuntu 22.04
  • Other related components versions: fedcloud version 1.2.15

Steps to reproduce

  • Provision a new VM
  • Install fedcloudclient
  • Set environment variable EGI_VO and EGI_SITE
  • Run command e.g. fedcloud openstack server list

Error message is shown:

Error: Missing one of the required mutually exclusive options from 'Site' option group:
  '--site'
  '--all-sites' / '-a'
@thebe14
Copy link
Collaborator Author

thebe14 commented Jun 17, 2022

Same thing happens on Windows (fedcloud version 1.2.14).

@tdviet tdviet added the bug Something isn't working label Jun 17, 2022
@tdviet
Copy link
Owner

tdviet commented Jun 17, 2022

Thanks for report. It is the bug of click-option-group library, concretely the classes RequiredAnyOptionGroup and RequiredMutuallyExclusiveOptionGroup, that check the requirements of parameters only via CLI options.

Fixing this bug properly requires more times. We can temporarily disable the requirement checking to make the fedclouclient work for your case. However if users forget to set site option, they will receive nonsense error messages "VO xxx is missing on site None".

@tdviet
Copy link
Owner

tdviet commented Jun 17, 2022

To be fixed in the planned fedcloud.config module, that will read config files + relevant environment variables during initialization and set all global variables (including default site and VO) accordingly, so we can ignore requirements checking via click-option-group.

@tdviet
Copy link
Owner

tdviet commented Jun 17, 2022

To be fixed in #86

@tdviet
Copy link
Owner

tdviet commented Nov 22, 2022

Disable support EGI_SITE ennvar and remove it from documentation. d889dbb

A systematic solution for setting site via config module (with a new envvar FEDCLOUD_SITE) will be introduced in the new major release. More info in #86

@tdviet tdviet closed this as completed Nov 22, 2022
gwarf pushed a commit to EGI-Federation/documentation that referenced this issue Feb 3, 2023
The FedCloud CLI was using an env var EGI_SITE to set the site on which
to operate. This is not working since a while now, because of a bug in a
Python lib. Details at
tdviet/fedcloudclient#150.

Thus I removed this from our user docs, will update when a workaround is
implemented in a new version of FedCloud CLI.
marcvs pushed a commit to EOSC-synergy/egi-documentation that referenced this issue Mar 9, 2023
The FedCloud CLI was using an env var EGI_SITE to set the site on which
to operate. This is not working since a while now, because of a bug in a
Python lib. Details at
tdviet/fedcloudclient#150.

Thus I removed this from our user docs, will update when a workaround is
implemented in a new version of FedCloud CLI.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants