Closed RedChops closed 5 years ago
Could you show the details you filled in the compute profile form?
Might make more sense to type out my changes here rather than a very long screenshot. If I don't note it here, I left it at the default:
Type: KVM/Qemu server
Qemu Agent: [x] KVM: [x]
Cores: 4
Memory: 8589934592 Minimum memory: 1073741824 Ballooning Device: [x] (Note: What unit are these memory settings supposed to be? Given the default I assumed bytes, but I also tried megabytes)
Storage: ceph Controller: SCSI (I've tried each of the four: IDE/SATA/SCSI/VirtIO Block) Device: 0 (Also tried setting this to '1' just to be sure) Cache: No cache Size: 34359738368 (Again, given the default I assumed byte, but also tried megabyte)
This issue is relative to foreman_fog_proxmox and not fog_proxmox.
DiskHelper.extract_controller accepts a/(\w+)(\d+)/
string id (e.g. scsi0
) but it is not.
Sizes must be formatted in text (e.g. 1 Gb) by foreman javascript. But it seems not to.
Have you installed the plugin javascript: /usr/bin/foreman-ruby /usr/bin/bundle exec bin/rake plugin:assets:precompile[foreman_fog_proxmox]
?
Hm, I lack the foreman-ruby binary, but I do have a foreman-rake binary. After setting proper permissions in the ruby gems folder (foreman-rake su's to foreman user), running /sbin/foreman-rake plugin:assets:precompile[foreman_fog_proxpox]
, and restarting the foreman service, the javascript formatting you mention now works.
I'm unsure if this is related, but several settings don't seem to 'stick': If I set 4 cores under CPU, 8 Gb for memory, 1 Gb for minimum memory, and check ballooning device, the only setting out of that batch that sticks is the 8 Gb memory setting. All other settings from my above writeup do stick in the configuration.
1- Do you still encounter the error?
2- Could you post another issue in foreman_fog_proxmox related to the server VM settings issue?
Sorry yes, this issue has been resolved. With this comment I'll close the issue and open a new one in foreman_fog_proxmox.
For posterity, the tasks that fixed this for me are as follows (since they differ slightly from the instructions in the README.MD file)
sudo chgrp -R foreman /opt/rh/rh-ruby24/root/usr/local/share/gems/gems
sudo chmod g+w /opt/rh/rh-ruby24/root/usr/local/share/gems/gems
sudo foreman-rake plugin:assets:precompile[foreman_fog_proxmox]
Describe the bug After filling out the details of the compute profile and pressing submit, the page reloads and does not reflect any of the changes. Pressing cancel takes me back to the list of available hosts and shows that the profile was saved. Clicking on that profile again gives me the message mentioned in the bug title. The stack trace seems to suggest an error with the controller, but I get this error no matter what drive controller I select.
To Reproduce Steps to reproduce the behavior:
Expected behavior The details I filled in should be displayed to me. (This profile also gives the same error when trying to create a host using it)
Versions fog-proxmox: 0.5.1 foreman_fog_proxmox: 0.5.1 foreman: 1.18.2
Stack trace