Open brendan4linux opened 2 months ago
Which foreman_fog_proxmox and fog-proxmox version you are using?
Thank you very much for the quick response, we are using the following, which (I believe) was installed by foreman-installer:
[root@
And if helpful, the foreman-installer setting showing enabled:
[root@
Thanks, please let me know if I can provide anything else :)
Hey hey, wanted to give this one a bump and see if anyone had any idea of what the problem/problem domain might be for this one?
If not, i'd like to ask if someone familiar with the plugin may have an idea of which file(s) or methods this problem may reside in? While i'd prefer to leave it to the pros, the amateur coder in me would love to have a look - if I can find a 'fix' maybe I can submit a pull request, just a thought.
Thanks for an amazing product btw, been using Katello for years and it's saved my job/sanity.
Describe the bug When editing an associated VM in Foreman 3.11 (Katello 4.13), even when making unrelated (Puppet ENC/Parameter changes), it appears Foreman will try to change something on the VM's disk, which causes Proxmox to error with the following. It also creates a duplicate (And unused) disk on the Proxmox side, even though it errored:
To Reproduce Steps to reproduce the behavior:
Expected behavior No changes/duplication to the disk - expected only relevant/changes items to be modified on the Proxmox guest
Screenshots
Desktop (please complete the following information):
Additional context Tested on Proxmox VE 7.2, 7.4, and 8.2, with both BIOS and UEFI builds - please let me know if I can help in any way/test any fixes and thank you!