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

Fail fast when access to registration service is forbidden #13

Open
mcalmer opened this issue Apr 2, 2024 · 1 comment
Open

Fail fast when access to registration service is forbidden #13

mcalmer opened this issue Apr 2, 2024 · 1 comment
Assignees

Comments

@mcalmer
Copy link

mcalmer commented Apr 2, 2024

The use case:

A customer has only BYOS instances and a total isolated network where no access to a not company network is allowed.
Also no access to the cloud registration service is possible.

The customer manages the instances with SUSE Manager.
SUSE Manager is calling instance-flavor-check on all clients to find out if they are BYOS or PAYG.
This cause now delays and performance problems as the tool always need to reach a timeout before it can report BYOS.

Possible options to come around this:

  • configuration option to disable this and directly return BYOS
  • environment variable to achieve this
  • reduce timeout or intelligent detection that the service cannot be reached.
  • etc...

See also: https://bugzilla.suse.com/show_bug.cgi?id=1218305#c59 and also https://bugzilla.suse.com/show_bug.cgi?id=1222134

@jesusbv jesusbv self-assigned this Apr 17, 2024
@jesusbv
Copy link
Collaborator

jesusbv commented Apr 26, 2024

In order to mitigate the performance impact on the request timeout, a timeout of 10 seconds (as agreed) instead of letting the request timeout with its default (longer) value

To help with the users with no network, a new flag like --retry-attempts defaulting to 3 would help
so one could call the command with 0 and would have to wait 10 seconds (1 request) to get the value

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

No branches or pull requests

2 participants