Bug #28032
closed
tfm-rubygem-foreman_fog_proxmox package issue
Added by Tania Hagan almost 5 years ago.
Updated about 1 year ago.
Description
Hi,
I installed the tfm-rubygem-foreman_fog_proxmox 0.8.0 with foreman 1.23.0, katello 3.13.0, and centos 7. However when attempting to create a compute resource via Infrastructure -> Compute Resources, I got the following message:
Unable to save
`:disable_proxy` parameter and `:proxy` parameter cannot both be set at the same time.
I reported the issue here https://github.com/theforeman/foreman_fog_proxmox/issues/106 and was given recommendations to install the proxmox plugin directly from git. This worked for me, and I referred here to report the issue.
Thank you,
Tania
As far as I analysed this issue, this is due to the fact that the 0.8.0 version of fog-proxmox on https://rubygems.org (that foreman-packaging uses) has multiple bugs.
I am not sure what commit from git was used to create it, since there is no tag for version 0.8.0 on github and my latest search did not find the problematic code in any of the latest commits.
Tristan Robert, can you shed some light on this.
The cleanest way to solve this would be to release a new bugfix version (e.g. 0.8.1) of fog-proxmox to rubygems and use that one.
A not so clean solution would be to create our own gem version from the latest master of fog-proxmox and push it to foreman-packaging.
I could create a PR for the not-so-clean solution, I think only Tristan Robert can push new releases to https://rubygems.org/gems/fog-proxmox.
- Triaged changed from No to Yes
- Status changed from New to Need more information
There have been updates to this gem. Is it still an issue?
- Status changed from Need more information to Rejected
Also available in: Atom
PDF