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

Unexpected error message when configuring ComputeRessource with invalid user token #217

Open
neomilium opened this issue Dec 14, 2021 · 4 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@neomilium
Copy link
Contributor

Describe the bug
During the creation or modification of a Compute Ressource, after selecting the user token auth method and filling all fields with invalid token, I tested connection with the provided button.
It replied an Proxmox version Unknown is not semver suitable error.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Compute Resources, create or modify an existing one
  2. Set authentication method to User token
  3. Fill form with invalid user token
  4. Use the Test connection button
  5. See error:
Unable to save
ERF42-4050 [Foreman::Exception]: Proxmox version Unknown is not semver suitable

Expected behavior
Raise an error about invalid credentials.

@inetshell
Copy link

I'm also getting this issue. I tested with the following versions:

  • Foreman 3.6.0-develop
  • PROXMOX 6.4-15 and 7.3-3

@tristanrobert I'm thinking about sponsor your project if it's still alive.

@inetshell
Copy link

I just tried using "access ticket" instead of token and worked for PROXMOX 6.4-15 and 7.3-3.

@tristanrobert tristanrobert self-assigned this Nov 26, 2022
@tristanrobert tristanrobert added the bug Something isn't working label Nov 26, 2022
@tristanrobert tristanrobert added this to the 0.15.0 milestone Nov 26, 2022
@tristanrobert
Copy link
Collaborator

I have a few time now to work on it. Sponsor would help me to get more time. Thank you. I am working on v0.15.0. I have already fixed some major bugs. I test it and again and again before merging very soon.

@pdolinic
Copy link

pdolinic commented May 5, 2023

I can confirm this bug, you can just use the 2nd option of access_ticket for a workaround as of now.

  1. Firstly create a real Linux root_user (Proxmox won't do that for you)(your_new_root_user), then -> add that Linux user to Proxmox(your_new_root_user@pam), then
    (assuming you you want to grant maximum permissions for testing without worring about security)
  2. Go to datacenter -> permissions -> add -> user permissions and add: path \ , user: your_new_root_user@pam, Role: Administrator , Propagate checked

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

4 participants