-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
vmid not auto set when creating from Foreman API #254
Comments
I ran into the same issue when trying to provision a host on Promox using Hammer CLI:
|
Manisha15
added a commit
to ATIX-AG/foreman_fog_proxmox
that referenced
this issue
Feb 12, 2024
Manisha15
added a commit
to ATIX-AG/foreman_fog_proxmox
that referenced
this issue
Feb 12, 2024
Manisha15
added a commit
to ATIX-AG/foreman_fog_proxmox
that referenced
this issue
Feb 12, 2024
Manisha15
added a commit
to ATIX-AG/foreman_fog_proxmox
that referenced
this issue
Feb 12, 2024
Manisha15
added a commit
to ATIX-AG/foreman_fog_proxmox
that referenced
this issue
Feb 12, 2024
Manisha15
added a commit
to ATIX-AG/foreman_fog_proxmox
that referenced
this issue
Feb 20, 2024
Manisha15
added a commit
to ATIX-AG/foreman_fog_proxmox
that referenced
this issue
Feb 21, 2024
Manisha15
added a commit
to ATIX-AG/foreman_fog_proxmox
that referenced
this issue
Feb 21, 2024
Manisha15
added a commit
that referenced
this issue
Feb 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Bug
Creating hosts through the web ui works correctly, however attempting to do it through the api returns the error
Backtrace for 'Action failed' error (ArgumentError): vmid is required for this operation
To Reproduce
Attempt to create a host through the API with a host group that defines using a proxmox compute resource. Sample python used:
Expected behavior
As with the webui, the plugin should get the next vmid automatically.
Additional context
If a valid VMID is specified manually (by uncommenting the
'vmid': 123
undercompute_attributes
) it works perfectly, but that is not easily workable for this script. Additionally passing any string tovmid
that isn't a valid proxmox vmid results in the host being created in foreman, but silently failing to do anything in proxmox. Subsequent efforts to edit the VM in foreman will return the errorVersions
Foreman: 3.6.1
rubygem-fog-proxmox.noarch: 0.15.0-1.el8
rubygem-foreman_fog_proxmox.noarch: 0.14.2-1.fm3_7.el8
The text was updated successfully, but these errors were encountered: